You’re offline. This is a read only version of the page.
Announcements
55
Apologies, I know this is basic database structures but I'm struggling with a few scenarios. I'm building out a case management solution for IT faults and there are several situations where I don't know whether or not an attribute should be it's own table.
For example 'incident status', this would be a small list of case states (New, In Progress, On Hold, Pending closure, Closed), I can't at this time think of any attribute beyond 'name' and would normally just have this as an attribute of the 'incident' table, but in my current commercial application this is a separate table... am I missing something?
Hi @johnbradbury,
In general for future proofing especially if this is more of a large solution that is subject to have lots of enhancements, make is a separate table. See tip #9 and #10 at: https://powerusers.microsoft.com/t5/Power-Apps-Community-Blog/Top-15-best-practices-when-configuring-Power-Platform-and/ba-p/850804
Hope this helps!
Share
Report
All responses (
Answers (
