When we work in SMAX Go or FSA platforms. We work with different SFMs, Lets say a child section is having number of records and we keep adding some records in the child section. At this time there is a parity issue when SMAX Go and FSA environments are concerned.
Request you to keep both products in parity where the indexing order in the background should always be in the same order as in the UI.
What is the underlying problem do you intend to solve with this idea?
Indexing order in the background should always be in the same order as in the UI
How is the problem being addressed today, if at all?
This is addressed by providing proper training to the user.