Skip to content

fix: add custom attributes to data set section [DHIS2-7765]#970

Open
Sharmyn28 wants to merge 1 commit into
masterfrom
DHIS2-7765
Open

fix: add custom attributes to data set section [DHIS2-7765]#970
Sharmyn28 wants to merge 1 commit into
masterfrom
DHIS2-7765

Conversation

@Sharmyn28

@Sharmyn28 Sharmyn28 commented Jun 12, 2026

Copy link
Copy Markdown
Contributor

Fix attribute:

  • Attributes: choosing Applies to Section
  • Add custom attributes into Data set Section Form

DHIS2-7765

Custom attributes (data set section form)
image

@netlify

netlify Bot commented Jun 12, 2026

Copy link
Copy Markdown

Deploy Preview for dhis2-maintenance-app-beta ready!

Name Link
🔨 Latest commit a6f3487
🔍 Latest deploy log https://app.netlify.com/projects/dhis2-maintenance-app-beta/deploys/6a2c48620055b2000819a764
😎 Deploy Preview https://deploy-preview-970.maintenance-app-beta.netlify.dhis2.org
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

@Sharmyn28 Sharmyn28 marked this pull request as ready for review June 12, 2026 17:56
@sonarqubecloud

Copy link
Copy Markdown

@Sharmyn28 Sharmyn28 requested a review from a team June 15, 2026 07:45

@tomzemp tomzemp left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

I wonder if we should change the attribute description from section to data set section (would be better in a separate ticket though as it would require a bunch of documentation updates)

Just while testing it, it made me realise that if you remove an attribute from a certain object, you can end up with "legacy" attribute values which we will not display. I think we probably want to address that, e.g. let you see what was previously saved and then remove it on save (this is not specific to this ticket, so I'll add it as a discussion point for one of our upcoming meetings)


<CustomAttributesSection
schemaSection={dataSetSectionSchemaSection}
sectionedLayout={true}

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this could also just be sectionedLayout which is more consistent with how it's written elsewhere in the app, but explicitly passing true also works

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants