@chandukasani I know it looks very nice if you use a naming convention for you Fabric items, but why bother adding prefixes to every item?
- You always see the type of the item in the view.
- You can use task flows to assign items to different tasks.
- When you need to select a specific item, for example a Lakehouse item, you will only get to see Lakehouses and also see in which workspace the item is in.
- Does it matter if it's a data engineering or a data science item?
- When non-IT users start to create their own items, they don't bother following your naming convention.
- Don't use prefixes for items like semantic models, reports, dashboards and organizational apps. Name them so everyone can easily understand what they are for or contain.
Hope this helps. If so, please give kudos 👍 and mark as Accepted Solution ✔️ to help others.
