Unanswered

How to Create Multiple Tables with the Same Name in Dataverse

(0) Share

Report

Posted on by PN-95-home

Hello my dears!

I recently purchased an Microsoft 365 Business Basic subscription to make use of Microsoft Dataverse with Microsoft PowerApps.

I am in the "default" Environment and have created two empty solutions (using the same publisher):

- SolutionA

- SolutionB

Each of my solutions will need a table named "Tasks", but with completely different data and slightly different column names and types.

While I can create a "Tasks" table as expected in SolutionA, I unexpectedly receive an error message while trying to create a "Tasks" table in SolutionB:

Failed to create entity with logical name pn95_tasks and object type code -1.

Exception: Microsoft.Crm.CrmException: The schema name pn95_Tasks for type Entity is not unique.

An pn95_Tasks with same name already exists.

at Microsoft.Crm.Metadata.SchemaNameValidator.ValidateSchemaNameIsUnique(String metadataEntityName, String attributeName, ISqlExecutionContext sqlContext)

at Microsoft.Crm.Metadata.EntityService.ValidateEntitySchemaNameForCreate(String entityName, String physicalName, Boolean isBPFEntity, MetadataHelper metadataHelper, ISqlExecutionContext sqlContext)

at Microsoft.Crm.Metadata.EntityService.ValidateEntityNameAndLabels(EntityCreateInfo entityInfo, MetadataHelper metadataHelper, ISqlExecutionContext sqlContext)

at Microsoft.Crm.Metadata.EntityService.ValidateForCreate(EntityCreateInfo entityInfo, MetadataHelper metadataHelper, ExecutionContext context, Boolean useReserveEntity)

at Microsoft.Crm.Metadata.EntityService.<>c__DisplayClass46_0.<CreateEntityFromReserve>b__0()

at Microsoft.PowerApps.CoreFramework.ActivityLoggerExtensions.Execute[TResult](ILogger logger, EventId eventId, ActivityType activityType, Func`1 func, IEnumerable`1 additionalCustomProperties)

at Microsoft.Xrm.Telemetry.XrmTelemetryExtensions.Execute[TResult](ILogger logger, XrmTelemetryActivityType activityType, Func`1 func)

at Microsoft.Crm.Metadata.EntityService.CreateEntityFromReserve(IEntityInfo entityInfo, MetadataHelper metadataHelper, Boolean isInSolutionImportMode, ExecutionContext context, Guid& entityId)

at Microsoft.Crm.Metadata.EntityService.CreateInternalHelper(EntityCreateInfo entityInfo, MetadataHelper metadataHelper, Boolean shouldCreateOnlyFromReserve, ExecutionContext context)

What I am noticing from this is that solutions are not isolated containers (as I had wrongly assumed).

Does it mean that I need to create a new environment for each app, to use tables with the same name but with different compositions or is there a way to create a table, which is scoped to be only accessible within a solution?

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (2)

Answers (0)

v-bofeng-msft Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!
Hi @PN-95-home ,

Table names are unique to an environment, so it is not possible to create multiple tables with the same name. If you insist on using the same table name and need different apps to access different data. Then you can add a field to distinguish the data, for example:

Add an 'APP' column

APP A only accesses the record in the table with the APP field value "A". The code should be:Filter(Table,APP="A")

APP B only accesses the record in the table with the APP field value "B". The code should be:Filter(Table,APP="B")

In addition, you could consider adding all the columns you need to this table, and different apps can use different fields as needed.

Best Regards,

Bof

Was this reply helpful? Yes No
Fubar 8,487 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Schema names are unique to each environment, the Display Name can be duplicated (you just need to alter the schema field before you hit save to avoid the error message you were getting).

Note: the out of the box Task is a 'special' Table and so generally not wise to try to duplicate it in the same environment. Emails, Tasks, Appointments can sync to Exchange (if setup) - also for that reason not advisable to heavily customize them.
Also, with an appropriate Business Unit structure and Security Role Table permissions you can achieve separation and segregation of data and make use of the same Tables with data not visible to different sets of users etc.

Was this reply helpful? Yes No