SAIL interface works in one environment, but not the other.

#SAIL Interface Issue with Dynamic Link.
We have a Selecte-able paging grid ruining from Query Rule (in with) with page size of 10.
The Data in this paging grid can be clicked on by dynamic link , where we are trying to store the data row on the user click.
The row of the grid is selected and we have toe correct information in two of our environments, but in one environment, it doesn't seem to work, the paging grid keeps refreshing on the user click, this doesn't happens in other environments

Code Snipet :
=load(
local!RptPagingInfo:a!pagingInfo(startIndex :1 , batchSize :10),
          local!userAttribute : rule!getUserAttribute(
user : ri!user
).attribute,
local!selectedAttribute:if( length(local!userAttribute) >1 , "", local!userAttribute),

          with(
local!viewReport :
rule!FMA_queryViewReport(
userAttribute : local!userAttribute ,
pagingInfo :local!RptPagingInfo),

if( length(local!selectedAttribute) >1 ,
a!sectionLayout(
label : ""...

OriginalPostID-210906

OriginalPostID-210906

  Discussion posts and replies are publicly visible

  • ...,
    firstColumnContents : {
    a!gridField(
    labelPosition: "ABOVE",
    totalCount: local!viewReport.totalCount,
    columns: {
    a!gridTextColumn(
    label: "userAttribute",
    field:"userAttribute",
    data: index ( local!viewReport.data, "userAttribute",{})
    ),
    a!gridTextColumn(
    label: "rpt field",
    field : "rpt_Field_1",
    data:
    index ( local!viewReport.data, "rpt_Field_1",{}),
    links: apply(
    rule!report_Dymanic_Link(
    data : _,
    selectedLink :local!selectedLink ,
    selectedRecord:local!selectedRecord,
    selecteduserAttribute :local!selecteduserAttribute ,
    showDetails :ri!showDetails

    ),
    local!viewReport.data
    )

    ...
  • ... )
                        }
                        value: local!RptPagingInfo,
    saveInto:local!RptPagingInfo
    )
    }
    ), /*Report Grid Details*/
    {} ).......
    )


    rule!report_Dymanic_Link
    a!dynamicLink(

    value: ri!data,
    label:ri!data.rpt_Field_1,
    saveInto: {
    a!save(ri!selectedGpbr , ri!data.gpbr),
    a!save(ri!selectedLink, "rpt_Field_1"),
    a!save(ri!selectedRecord, ri!data),
    a!save(ri!showDetails , true()),
    }
    )






  • Typically issues like this are related to the data source on one sever being out of synch with the other environments. I would start by ensuring the problem server/DS has the correct data, fields, etc - and go from there.
  • Usually when you have a problem in one environment and not the other, it will be a back end issue. I would suggest making sure your data store verifies first. Then go into your tables and check your data. It may just be an issue with old data.
  • I have looked at the database Views - compared between the environment. It doesn't seem to be as issue. I dont know what to make out of this. As per my analysis, as soon as I click on the dynamic link on the paging grid, the grid was refreshed and the brought a different data set all together. The current work around for now is, I have removed the sorting ability from the other columns and the used one column to be included in the sort info in paging info.
    I dont know how to solve this one. Any help would be highly appreciated.