Forum Discussion

pierre david's avatar
pierre david
Copper Contributor
Oct 26, 2017
Solved

Date of release of Column formatting in SP Online Modern experience

Hello, Have received a mail about a new feature : Column Formatting on modern experience Lists. But I see nothing in my First Release Tenant. Did I look at the good place ? If I'm good, do ...
Column Formatting
SharePoint Online
  • jcgonzalezmartin's avatar
    jcgonzalezmartin
    Oct 26, 2017
    AFAIK, the roll-out is still being done by Microsoft but we don't have specific dates about when the roll-out will reach your tenant
Anonymous's avatar
Anonymous
Nov 17, 2017

Really like the idea behind this feature, albeit a little tricky to play with the json. Not really a general user feature, perhaps a GUI one day? PowerApp editor?

 

Couple of things I have noticed:

  1. When formatting a Date, to go red when overdue, one of other my fields a calculated date one changes its format to UTC format. Which for general users is not really that readable.
  2. When clicking on the column, there used to be an edit menu item, this allow a person to change the setting on the field without needing to go into Library or List settings (the old SharePoint, way of doing it) which was less intimidating for new users.
  3. The schema file ("$schema": "http://columnformatting.sharepointpnp.com/columnFormattingSchema.json") is missing some syntax for operators ... "?" being a key one. 
  4. Using the $Fieldname, it took me a bit to figure out that spaces in the field name are put in as _x0020_ be good to put that in the documentation.

 

 

 

 

Clint Lechner's avatar
Clint Lechner
Iron Contributor
Nov 17, 2017

NOTES ON LOOKUP COLUMNS

 

  1. Depending on where you look, the documentation on accessing lookup column values isn't consistent.

    • "[$AssignedTo.title]"     --    correct
    • "[$AssignedTo].title"     --    incorrect (the right bracket is in the wrong spot)

  2. For people columns, the lookup data you want to retrieve IS LOWER CASE.  Even though the documentation gives an example, it can be easy to overlook because of how we all references lookups in the past whit People columns. 

    • "[$Manager.title]"     --    correct
    • "[$Manager.Title]"     --    incorrect ('Title' should be 'title')
    • "[$Manager.email]"     --    correct
    • "[$Manager.Email]"     --    incorrect ('Email' should be 'email')
  • jcgonzalezmartin's avatar
    jcgonzalezmartin
    MVP
    Nov 17, 2017

    Hey all, Microsoft promised at Ignite that column formatting will evolve in the future so customization will be possible without having to deal with JSON.  What I think is very important is to fix documentation problems identified here cc AaronMi LincolnDeMaris

    • LincolnDeMaris's avatar
      LincolnDeMaris
      Icon for Microsoft rankMicrosoft
      Nov 22, 2017

      Thanks everybody for pointing out errors in our documentation.  These have been corrected.

      • Anonymous's avatar
        Anonymous
        Nov 22, 2017

        Thanks for doing that ... the json parses better now :)

Resources