Forum Discussion
Helper IUpdateFromGit fails with CopyOverwriteUsageException - no API option to bypass deletion consent?
Hi yazdanb,
XMLA schema pre-apply (your CopyOverwriteUsageException workaround): ✅ Works with a Service Principal, it can connect to the XMLA endpoint and run the TMSL alter for column type changes. Your existing RLS role definitions in model.bim survive untouched.
updateFromGit with a semantic model: ⚠️ Unreliable with a Service Principal. In practice you need to run it with the credentials of the semantic model owner via a PAT token. (Microsoft Fabric Community)
RLS role membership via XMLA: ❌ Hard block. Service Principals cannot be added as model role members through the XMLA endpoint. (Microsoft Learn) Role definitions (the DAX filter expressions) are fine, but assigning users to roles is not.
Solution: Use your Service Principal for everything except the semantic model Git sync step, swap in a dedicated deployment user's PAT just for that one call. It's not clean, but it's the only reliable path today.
Memorable MemberHi yazdanb,
XMLA schema pre-apply (your CopyOverwriteUsageException workaround): ✅ Works with a Service Principal, it can connect to the XMLA endpoint and run the TMSL alter for column type changes. Your existing RLS role definitions in model.bim survive untouched.
updateFromGit with a semantic model: ⚠️ Unreliable with a Service Principal. In practice you need to run it with the credentials of the semantic model owner via a PAT token. (Microsoft Fabric Community)
RLS role membership via XMLA: ❌ Hard block. Service Principals cannot be added as model role members through the XMLA endpoint. (Microsoft Learn) Role definitions (the DAX filter expressions) are fine, but assigning users to roles is not.
Solution: Use your Service Principal for everything except the semantic model Git sync step, swap in a dedicated deployment user's PAT just for that one call. It's not clean, but it's the only reliable path today.