You don’t specify a version here, but since the view that a user sees is driven by their use profile, and the Restore Defaults essentially removes any changes a user had made, I believe it defaults to the column organization as defined within the IFS code itself.  

Pre-IFS Cloud in IEE I believe this is defined by the API coding itself, which is running a select that I expect to output in the order of the selection.  You could see this in the DB code/calls.

In IFS Cloud or Aurena I don’t know for sure but I would expect it to be defined by the order of the response from the REST API call for the presentation.  If this is true then the documentation in API Explorer would presumably give you that structure.

Not a 100% certain answer for you but this is where I would look.

HTH,

Nick

Hi ​@NickPorter 

It’s in 24R1.  Thank you.  We’re curious if it does default to a system defined layout, what happens to the setting that are in the Context to which the user is assigned?  If we had items in the context that are defined to be hidden, or different conditional settings, restore defaults would wipe out all of that?  Would a restart of the application, or refresh of the browser, cause the columns to revert to the settings of the context?

/Patrick

Not being on Cloud yet myself I cannot test, but in this scenario I would *guess* that it would revert to the definition in the Context, similar to how it would have reverted to what was seen from a ‘Base Profile’ pre-Cloud if one was assigned.