Leveraging Synchronize Scroll on Same List Structure with and w/o Time
Hi Everyone,
Looking to see how others are addressing a certain build request. We commonly get the request to have attribute information next to a metric that is also dimensioned by time. An approach we have started using is having two modules on the same UX page leveraging synchronize scroll. This allows us to have flexible time filtering/aggregation while also showing relevant information for line items. There are some inherent drawbacks. You have to turn off the native filtering/sort and add specific filters otherwise the views can get out of sync.
What are some other approaches being used for this type of request?
Additionally, users will request being able to export and import back into these modules which presents another challenge. Ideal situation would be to export all of the data together in one output for ease of use for the end users. A couple possible solutions we have thought of:
1. Have users export both modules, combine with copy and pasting in excel. Make adjustments and then import as 1 file using 2 export actions within a process.
2. Create a template module that has time periods as a line item along with the attributes to export as a single file. I personally do not like this approach do to the maintenance required for a yearly model rollover.
3. Create a template module that has "relative" time as a line item along with the attributes to export as a single module (1 is understood to always be associate with the first period in time range of the module, Ex. 1 = Jan 2025, 2 = Feb 2025). Then create a module to map the relative time back to the native time on the import.
Any other ideas?
Best Answer
-
Hi @Taylor Moore ,
For the import & export, you can create a staging layer & set the exports & imports from that.
The flow would be —> Export from staging module - User Updates a single file - Imports back to staging layer - Create separate saved views to update the other 2 modules - Imports to the final modules.
The attributes can be set as properties. I know this goes against the planual but it'd help you achieve a cleaner export view with the properties also in columns along with time in columns. Since this is a staging layer, you could always clear the list after the data is pushed into the main modules.
On the views, you could add these line items as subsidiary views in the module & use filters to only show these line items for the first month. So it'd look something like this & you could then let users filter/sort using native functionalities-
Hope this helps! :)2
Answers
-
Thank you @devrathahuja! I always forget about the ability to include properties like that in an export.
That's a creative solution for the view with the attribute data and time. Have you found a way to have those attributes be editable by the user without having to click into a subsidiary view?
0 -
@Taylor Moore - No I believe that won't be possible. You could create a user entry grid on a separate page or at the top of the page where users define the attributes & in this report they mainly view/filter/work with the data.
0