microsoft / microsoft/Dataverse-skills
Form generator issue with filed logicalname
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 226
- Forks
- 61
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 7
Description
i suggest to add :
Dataverse form XML datafieldname must use the attribute's LogicalName (always lowercase, e.g. exp_date), not the SchemaName (MixedCase, e.g. exp_Date). A MixedCase datafieldname is accepted and stored without error, but the control is silently dropped at render time — the field just never appears on the form, in both the runtime client and the maker portal designer.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the form generator and trace how Dataverse form XML datafieldname values are produced. Compare the generated value with the attribute LogicalName and SchemaName examples in the issue, then verify that fields render in both the runtime client and maker portal designer. Done means MixedCase SchemaName values no longer cause the control to be silently dropped.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- xml
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100