Unanswered

Dataverse table naming conventions for different environments

(0) Share

Report

Posted on by HilePow

I am currently working on a powerapps application with dataverse for storage. Initially I built my solution in my dev environment and moved it as a Un-managed solution for testing to test-env.

After finding some issues I started adding to the solution in test_env new flows, tables etc. Then I noticed to access the values of the new tables in my app I had to add prefix(crde##_solutionprefix_colName) when accessing the table items in gallery.

I didn’t have to use the prefix initially at my dev_env.

Now I have multiple naming conventions in my solution for my tables and app galleries items, how can I remedy this situation.

Only develop in dev environment?

Would this cause a problem going forward publishing the app in the production environment?

Also any material on solution and environments

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (7)

Answers (1)

AhmedSalih

6,678 Moderator on at

Like (0)

Report

Hello, @HilePow, When you create a solution in the Microsoft Power Platform, you can set a custom prefix. (This is a best practice). Then, all the objects that you create inside that solution will have that prefix. Having objects with different prefixes won't cause issue in your production environment but it is not easy while developing and integrating with other systems and data source (it will cause some confusion).

If my reply helped you, please give a 👍 , & if it solved your issue, please 👍 & Accept it as the Solution to help other community members find it more.

I am primarily available on weekdays from 6-10 PM CT and 5-10 PM CT on weekends.

Visit my Blog: www.powerplatformplace.com

Was this reply helpful? Yes No

HilePow 18 on at

Like (0)

Report

Thank you for the response 🙏
Follow up Question:
So currently I am working on the solution in my test_env and solution initially created in dev_env…
so I have a Two Collections:
colTableFromDev: create in dev when solution created initially
colTableFromTest: created in test
when accessing the collection elements in a gallery I can call normally call colTableFromDev.colName but for colTableFromTest.cre#_colName

is there any particular reason why powerapps is calling one with prefix the other one without?

Was this reply helpful? Yes No
AhmedSalih 6,678 Moderator on at

Like (0)

Report

@HilePow, It seems to me one is using the Display Name and the other, in test, is using the logical name of the column. When you created this table in the Test environment, did you initially created it inside the solution or it was added as existing table?

Was this reply helpful? Yes No
HilePow 18 on at

Like (0)

Report

I actually created the table outside the solution and added it into the solution at a later time.

Was this reply helpful? Yes No
Verified answer

AhmedSalih 6,678 Moderator on at

Like (1)

Report

@HilePow, That is why you see them with the “cre” prefix which is the default Published prefix.

Was this reply helpful? Yes No
HilePow 18 on at

Like (0)

Report

So I should be fine right going forward, no adverse effects on my app ?

Was this reply helpful? Yes No
Gary_Eden 375 on at

Like (0)

Report

A follow up to this topic along similar lines.

We use solutions and publishers to assign prefixes to Dataverse table names, which keeps them unique (under the covers). However, when selecting a data source (Dataverse tables) from with a PowerApp only the 'friendly' table name is visible.

The table may be unique due to the prefix but you can't find out which one you want without adding it first and checking what's in it. Time consuming but also risky if someone adds the wrong table and starts using it - we have several developers here.

Is there an easy way to identify which table is which?

Was this reply helpful? Yes No