Column formatting not saving for Single Line of Text Column

%3CLINGO-SUB%20id%3D%22lingo-sub-1170870%22%20slang%3D%22en-US%22%3EColumn%20formatting%20not%20saving%20for%20Single%20Line%20of%20Text%20Column%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1170870%22%20slang%3D%22en-US%22%3E%3CP%3ETo%20give%20some%20background%2C%20I%20have%20set%20up%20a%20SharePoint%20List%20to%20track%20part%20numbers%20that%20need%20to%20be%20cycle%20counted%20in%20our%20Manufacturing%20facility.%26nbsp%3B%20I%20recently%20the%20site%20to%20the%20new%20version%20of%20Sharepoint%20and%20now%20my%20part%20numbers%20show%20up%20in%20an%20unwanted%20format.%26nbsp%3B%20For%20example%2C%20a%20part%20number%20that%20used%20to%20show%20up%20as%20%225456226-599%22%20now%20looks%20shows%20up%20as%20%221001_.000%22.%26nbsp%3B%20%26nbsp%3BI%20entered%20in%20the%20below%20JSON%20and%20it%20appears%20to%20fix%20the%20issue%20when%20I%20select%20the%20%22Preview%22%20button.%26nbsp%3B%20However%2C%20After%20I%20save%20and%20close%20out%20of%20the%20formatting%20window%2C%20the%20part%20number%20column%20goes%20back%20to%20the%20unwanted%20format.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CEM%3E%7B%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3E%22%24schema%22%3A%20%22%3CA%20href%3D%22https%3A%2F%2Fdeveloper.microsoft.com%2Fjson-schemas%2Fsp%2Fv2%2Fcolumn-formatting.schema.json%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdeveloper.microsoft.com%2Fjson-schemas%2Fsp%2Fv2%2Fcolumn-formatting.schema.json%3C%2FA%3E%22%2C%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3E%22elmType%22%3A%20%22div%22%2C%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3E%22txtContent%22%3A%20%22%40currentField%22%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3E%7D%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1170870%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESharePoint%20Online%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1171309%22%20slang%3D%22en-US%22%3ERe%3A%20Column%20formatting%20not%20saving%20for%20Single%20Line%20of%20Text%20Column%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1171309%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F555621%22%20target%3D%22_blank%22%3E%40Rmkemmi%3C%2FA%3E%26nbsp%3Bdoes%20the%20default%20value%20of%20the%20single%20line%20of%20text%20column%20have%20a%20default%20value%20using%20a%20formula%20or%20anything%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERob%3CBR%20%2F%3ELos%20Gallardos%3CBR%20%2F%3EMicrosoft%20Power%20Automate%20Community%20Super%20User%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1172428%22%20slang%3D%22en-US%22%3ERe%3A%20Column%20formatting%20not%20saving%20for%20Single%20Line%20of%20Text%20Column%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1172428%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F174092%22%20target%3D%22_blank%22%3E%40Rob%20Elliott%3C%2FA%3E%26nbsp%3BThere%20is%20no%20formula%20-%20I%20believe%20the%20default%20value%20for%20the%20part%20number%20is%20just%20entered%20in%20plain%20text.%26nbsp%3B%20Many%20of%20the%20part%20number%20do%20have%20dashes%20(e.g.%2011-000-39)%2C%20so%20I%20don't%20know%20if%20that%20would%20have%20an%20impact%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1172663%22%20slang%3D%22en-US%22%3ERe%3A%20Column%20formatting%20not%20saving%20for%20Single%20Line%20of%20Text%20Column%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1172663%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F555621%22%20target%3D%22_blank%22%3E%40Rmkemmi%3C%2FA%3E%26nbsp%3B%20sorry%2C%20all%20I%20can%20suggest%20is%20that%20you%20create%20a%20new%20column%2C%20add%20in%20the%20data%20and%20see%20if%20the%20same%20thing%20happens.%20Without%20seeing%20it%20in%20action%20I%20don't%20know%20why%20the%20data%20would%20be%20being%20changed.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERob%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

To give some background, I have set up a SharePoint List to track part numbers that need to be cycle counted in our Manufacturing facility.  I recently the site to the new version of Sharepoint and now my part numbers show up in an unwanted format.  For example, a part number that used to show up as "5456226-599" now looks shows up as "1001_.000".   I entered in the below JSON and it appears to fix the issue when I select the "Preview" button.  However, After I save and close out of the formatting window, the part number column goes back to the unwanted format.

 

{
"$schema": "https://developer.microsoft.com/json-schemas/sp/v2/column-formatting.schema.json",
"elmType": "div",
"txtContent": "@currentField"
}

 

 

4 Replies

@Rmkemmi does the default value of the single line of text column have a default value using a formula or anything? 

 

Rob
Los Gallardos
Microsoft Power Automate Community Super User

@Rob Elliott There is no formula - I believe the default value for the part number is just entered in plain text.  Many of the part number do have dashes (e.g. 11-000-39), so I don't know if that would have an impact?

 

 

 

 

@Rmkemmi  sorry, all I can suggest is that you create a new column, add in the data and see if the same thing happens. Without seeing it in action I don't know why the data would be being changed.

 

Rob

When there is no JSON, it will still display the unwanted format mentioned in my original post.

Ryan