I am looking to move all of our “Line List” Event Reports from Event Reports to LineListing Application. There are a couple of instances where either the event report is not loading, or the event report no longer respects the correct ordering of dimensions put in place; in each instance, the line-listing does just fine.
My question is if I can I make a systematic, consistent edit to the eventVisualizations created in event report so that they can be “linelist” reports instead? Ideally I can do this without having to change the name/uid of the eventVisualization, as this will allow (hypothetically) the viz to continue to appear in dashboards where it already rests with addition changes or naming convention workarounds.
If I understand correctly, do you intend to make the change once or you mean by systematic and consistent that you will continue to use the older apps and as soon as the favorite is saved it will be under “line list” app?
I’m not sure I understand your point about the favorite and about it being a line listing object?
Basically the specific issues we’ve noticed is that for Line List option of Event Reports, the previous order respected (with categories, dataElements, etc. in columns of the line list) is no longer respected in v40 (whereas it was in v2.37). If we open the object in line-listing application it works, and if we save it can insert it into a dashboard where it also respects the order. So we have many of these objects, and ideally we could do a more bulk “adjust” to the objects to that they are “line listing app” objects vs. line list event report objects.
I put both versions (a line listing event report object and a duplicate saved in line listing app) in a dashboard and pulled them as a metdata dependency object, but can’t make out exactly what differences distinguish either as unique for the system.