Only module dependent UIDs are permitted for table DialogAEDSActionHasObject

Hi all

I saw this question already several times here in the forum. However I've not the problem by a Transport, the problem begun when I tried to add Object dependent reference from within Manager on a specific AccProduct. First I created just the AccProduct, then with the Method SwitchToModuleGuid() on that specific AccProduct I created the needed GUID. However afte having my GUID (CCC-CCFBBC5C6744064092199616B161AAB2), I tried to add the reference. OnSaving I get: [810312] Only module dependent UIDs are permitted for table DialogAEDSActionHasObject.

After searching this Forum I found the following post https://www.oneidentity.com/community/identity-manager/f/forum/30087/810312-only-module-dependent-uids-are-permitted-for-table-dialogtaggeditem-transport-file-error/73625#73625 where Markus asks to execute the following SQL-statement:

select ColumnName, IsUID, UID_DialogTable
from
 dialogcolumn
where ColumnName like 'UID%'
and IsUID = '0'

As a result I get:

ColumnName	                    IsUID	UID_DialogTable
----------------------------------------------------------------------
UIDLDAP                         False	LDP-T-LDAPAccount
UID_DialogColumn	            False	QBM-T-QBMVPwdPolicyColumns
UID_DialogTableReference	    False	QBM-T-QBMVPwdPolicyColumns
UID_DialogAEDSActionHasObject	False	QBM-T-DialogAEDSActionHasObject

So I guess the Problem is, that UID_DialogAEDSActionHasObject has set IsUID=False will give me the error. When I tried to reproduce this step in a fresh installed environment, the mentioned Attribute for UID_DialogAEDSActionHasObject is set to TRUE. Result is, I can add the object dependent reference.

Is it possible to update this attribute likewise?

Update DialogColumn
Set IsUID = 1
where 1=1
and ColumnName = 'UID_DialogAEDSActionHasObject' 
and UID_DialogTable = 'QBM-T-DialogAEDSActionHasObject'

... or will this end up in a inconsistency of the Database schema?

By the way, the result is the same for all Environments (development/integration/production), so would need to do this 3 times. All installation are running on the latest version v8.1.4 and all DB's have a migration background from Version 6 to 7 to 8, whereas the fresh installed environment which it worked was installed straight to version 8.0.1 and was migrated with every update up to 8.1.4.

Thanks for your advice
Kind regards,
Rolf Joggi