cancel
Showing results for 
Search instead for 
Did you mean: 

First line on the screen is not indexed as first line in SMAX Go And FSA

First line on the screen is not indexed as first line in SMAX Go And FSA

First line on the screen is not indexed as first line in SMAX Go And FSA

0 Likes

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.
Product Area?
SMAX Go and FSA
What version of ServiceMax are you on?
20.1
Tags (3)
1 Comment
Fry Chef
Fry Chef

Just to give more info regarding this. We encountered this problem while working with code snippets. We observed the lines which are added recently in child section, these lines are opposite in order with respect to code snippet lines in the backend.

Example:

Lines added in the UI 

Lines Added recently in the child sectionLines Added recently in the child section

 

When These lines are observed in code snippet using $sfm_records.get() api, being in opposite order.