Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add system property like __id back to entity CSV attachment? #1093

Open
ktuite opened this issue Feb 21, 2024 · 1 comment
Open

Add system property like __id back to entity CSV attachment? #1093

ktuite opened this issue Feb 21, 2024 · 1 comment
Labels
documentation API docs, readme, developer docs entities Multiple Encounter workflows

Comments

@ktuite
Copy link
Member

ktuite commented Feb 21, 2024

I was thinking about this comment on the forum about how someone fixed a problem with their form by replacing __id with name.

Because we build up the entity CSV differently for downloading it directly vs. attaching it to a form (though at one point they were the same), there isn't a way to directly look at the entity CSV that gets attached to the form.

Maybe we should document this better OR change the attachment CSV a little bit.

@ktuite ktuite added documentation API docs, readme, developer docs entities Multiple Encounter workflows labels Feb 21, 2024
@matthew-white
Copy link
Member

One thing we could consider is to make this an option when the user goes to download the entities CSV file. I think __id is a nice, clear column header outside of the context of OpenRosa clients. But I could also understand a user wanting to see exactly what's downloaded to clients.

Right now, it's not easy for users to see the CSV that's downloaded to clients, because we don't provide access to the form attachments of the published form version. Something else that might help is if we provided read-only access to published form attachments. Then users could see exactly what's being downloaded to Collect.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation API docs, readme, developer docs entities Multiple Encounter workflows
Projects
Status: 🕒 backlog
Development

No branches or pull requests

2 participants