web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Power Apps - Microsoft Dataverse
Answered

Naming convention for column names and option sets

(1) ShareShare
ReportReport
Posted on by 634
 
In my current solution I can add an option set Widget Status ( xyz_widgetstatus) .  However, I can also create choice column named Wiidget Status ( xyz_widgetstatus) .  Dataverse seems ok with this but will these cause me issues during the development, as both the column and the option set seem to have the same unique name.  Should I avoid the naming clash with a naming convention for my option sets.
 
 
 
 
Categories:
I have the same question (0)
  • westerdaled Profile Picture
    634 on at
    Naming convention for column names and option sets
    Hi really like both responses, so many thanks to @Abdul Wahab and @developerAJ.  I was bit surprised Dataverse allowed me to do it.  Anyway,  I have relayed both suggestions to the project team and will encourage them to adopt one of them.  I think the one suggested by @developerAJ will need us creating another solution ( publisher) to handle the new prefix.   
  • Verified answer
    developerAJ Profile Picture
    3,386 on at
    Naming convention for column names and option sets
    It’s best to avoid naming clashes between global option sets (choices) and columns in Dataverse, even though the platform technically allows it. For example, you could have both a global choice called xyz_widgetstatus and a column with the same schema name, but this can quickly lead to confusion during development. In Power Apps formulas, it may be unclear whether you are referencing the global choice or the column; in queries, plug-ins, or API calls, overlapping schema names can make troubleshooting harder; and in team development, other developers may struggle to differentiate which object is being used. To keep things clear and maintainable, it’s a good practice to adopt a simple naming convention that distinguishes global choices from local columns—for instance, prefixing global choices with gch_ (e.g., gch_widgetstatus) while leaving local columns with your usual prefix (e.g., xyz_widgetstatus). This ensures that your solution remains consistent, unambiguous, and easier to maintain in the long run.
     

    If this solution helped you resolve your issue, kindly mark it as accepted — it makes it easier for others to find and also closes the discussion. If you found it useful, a Like ❤️ would be greatly appreciated!

    🤝 Let’s connect on LinkedIn || 📘 Explore more on my articles

  • Suggested answer
    Abdul Wahab Profile Picture
    42 on at
    Naming convention for column names and option sets
    1. where problems arise
      1. Code / Plugins / Scripts: If you’re writing JavaScript, C#, Power Automate, or Power FX expressions, the overlap in names can make it confusing to understand whether you’re referencing the column or the choice definition.
      2. Future Maintenance: Another developer (or future you!) might see xyz_widgetstatus and not realize if it’s the column or the option set. Debugging gets messy.
      3. Upgrades & Migrations: If Microsoft changes rules in the future (or if you export/import solutions across environments), the name clash might cause import conflicts.
      4. API Usage: When using Web API or SDK, schema names matter. If both have the same schema name, your dev experience will be painful — you’ll often need to double-check what object you’re dealing with.
    2. Best practice (what most teams do)
      1. Use a naming convention to differentiate global choices vs. local columns. For example:
        1. Global choices (option sets): xyz_widgetstatusset or xyz_widgetstatus_global
        2. Table column: xyz_widgetstatus
    Abdul Wahab
    Direct: +923323281237
    Email: abdulwahabubit@outlook.com
    LinkedIn: https://www.linkedin.com/in/abdul-wahab-a5b8b011a/
    Twitter: https://twitter.com/Abdulwahabubit
    GitHub: https://github.com/AbdulWahabWarind
    YouTube: https://www.youtube.com/channel/UCBjgLqLK_2kU-3bwo4McrTw

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Tom Macfarlan – Community Spotlight

We are honored to recognize Tom Macfarlan as our Community Spotlight for October…

Leaderboard > Power Apps

#1
WarrenBelz Profile Picture

WarrenBelz 1,019 Most Valuable Professional

#2
developerAJ Profile Picture

developerAJ 436

#3
MS.Ragavendar Profile Picture

MS.Ragavendar 281 Super User 2025 Season 2

Last 30 days Overall leaderboard

Featured topics