Forum Discussion

Copper Contributor

Apr 11, 2024

Solved

update dataverse table with dataverse primary key results in datatype error

Hi all. I have an annoying issue. I use MS access front end, dataverse backend, I'm using a simple bit of VBA code, to add a new record in a table. This is triggered by clicking a button on a...

access

Dataverse

TheJaks
Jun 12, 2024
hi all - just a quick update if anyone stumbles across this issue:

Dataverse as a managed solution blocks overriding a foreign/ alternative key, you can only update the dataverse primary key. In an unmanaged solution it’s the reverse I think, you can only update the alternative key, not the dataverse primary key.

the dataverse primary key is a GUID which cannot be stored in a text box as per issues above (that will show up as ???? In VBA). Solution : it can be stored in a combo box as a workaround, which as it turns out is compatible with GUID.

George_Hepworth

Silver Contributor

Apr 11, 2024

I agree that Dataverse is a black box with its own internal workings and rules. I guess I am lazy, but I'd rather avoid the whole issue and rely on the known, tried and true SQL Server/SQL Azure. If someone else wants to adopt Dataverse, great, but the learning curve is mostly up and not very direct, IMO.

TheJaks

Copper Contributor

Jun 12, 2024

hi all - just a quick update if anyone stumbles across this issue:

Dataverse as a managed solution blocks overriding a foreign/ alternative key, you can only update the dataverse primary key. In an unmanaged solution it’s the reverse I think, you can only update the alternative key, not the dataverse primary key.

the dataverse primary key is a GUID which cannot be stored in a text box as per issues above (that will show up as ???? In VBA). Solution : it can be stored in a combo box as a workaround, which as it turns out is compatible with GUID.