Closed Parth7223 closed 1 week ago
@Parth7223 Sync Attribute' header should be populated in the sample CSV in case that is part of the UI for any project. (Should not be populated in CSV if not available in UI for any project) - this is already working like this
@mahalakshme Made code changes to do the following:
sample-usersAndCatchments - rwb.csv sample-usersAndCatchments - APF.csv sample-usersAndCatchments - Goonj.csv
UsersAndCatchement template file after description row changes
@himeshr looks good, but found a bug: looks like supported languages and user groups didn't get exported after the above fix.
Oh, my bad, not a bug, uploaded the template file and not the downloaded sample file.
@himeshr looks good, but found a bug: looks like supported languages and user groups didn't get exported after the above fix.
Sample file with description row changes. sample-usersAndCatchments.csv
Org : Akrsp,rwbniti env : staging
Please let me know if u need any clarification on this
@Dinesh2019 for 1 and 2 - The idea is to have description wherever it is confusing and keep it minimal. For Track Location, etc., it is evident that it can have only one value.For UserGroups from egs it is understandable/
So I think the first two can be skipped. If there are too many descriptions, user might not read it.
@Dinesh2019 regarding "And also for sync attributes we don't have space in between the values" the possible values as per the sample csv file would now be generated randomly to be one of
The desciption row, contains possible values that could be specified.. Ex: Yes, No Above example implies that the user can specify following values in the upload file.
Need:
Several tickets related to CSV have been raised since its usage is not user friendly. Below are some of the issues:
When a user belongs to multiple user groups, they need to be separated by
|
. But everywhere else generally the separator is,
https://avni.freshdesk.com/a/tickets/3902Even if the needed guidelines are present in readme, it is good to make the app usable for simpler cases as much as possible.
Acceptance criteria:
Sample CSV file to be downloaded: Link
,
separator instead of|
for UserGroups column for consistencyIgnore the below:
Inputs
Questions:
Generating dynamically based on different number of levels is more effort. So add notes like the ones below:
Proposed Behavior: Rather than generating a standard sample CSV for user & catchment across all the project, headers should be populated on the basis of configured values as mentioned below.