You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we are importing a layout with dataSet and that dataSet exists in our target CMS (with different dataSetColumnId's).
The logic is that we match the dataSet, we match the columns and then we go through each datasetview and ticker widgets in the source layout to find and replace dataSetColumnId's.
Unfortunately that's not working as expected at the moment.
Current logic is assuming that we have priorDataSetColumnId containing the dataSetColumnId's from the source, the issue seems to be that this parameter is empty - as such when we try to find columns Ids there to replace them we are not able to do that, hence nothing gets replaced.
priorDataSetColumnId is populated when we clone a dataSet, however we are not cloning dataSet when we've a matching dataSet in the target CMS, in fact we can't do that.
Source dataSetColumnId's are stored in the dataSet->dataSetColumnId we can use that or assign those values to the column->priorDataSetColumnId and then replace those with the column->dataSetColumnId in places where it matches other existing conditions.
We will need to investigate the best way to make it work in all cases.
The text was updated successfully, but these errors were encountered:
When we are importing a layout with dataSet and that dataSet exists in our target CMS (with different
dataSetColumnId
's).The logic is that we match the dataSet, we match the columns and then we go through each
datasetview
andticker
widgets in the source layout to find and replacedataSetColumnId
's.Unfortunately that's not working as expected at the moment.
Current logic is assuming that we have
priorDataSetColumnId
containing thedataSetColumnId
's from the source, the issue seems to be that this parameter is empty - as such when we try to find columns Ids there to replace them we are not able to do that, hence nothing gets replaced.priorDataSetColumnId
is populated when we clone a dataSet, however we are not cloning dataSet when we've a matching dataSet in the target CMS, in fact we can't do that.Source
dataSetColumnId
's are stored in thedataSet->dataSetColumnId
we can use that or assign those values to thecolumn->priorDataSetColumnId
and then replace those with thecolumn->dataSetColumnId
in places where it matches other existing conditions.We will need to investigate the best way to make it work in all cases.
The text was updated successfully, but these errors were encountered: