Problem with model in Fabric DW + pb in pipelines

[MylenePBI]

Hello, I am trying to work on my datawarehouse, but I have several problems. Everything was running well before my holidays, but now I am unable to create relation, remove table in default dataset (I don't even see the defaut dataset layout) etc...

Here the several errors that I have:

- I don't see the default dataset layout anymore. When I try to Manage the default dataset (adding a new table), here the type of error that I have:

Unable to update BI model with these changes. Please try again later or contact support.

You cannot change the storage mode of partition '<ccon>XXXXX</ccon>'. Converting existing tables or partitions from Import or DirectQuery mode to Direct Lake is not supported. See https://go.microsoft.com/fwlink/?linkid=2215281 to learn more.

- Trying to hide a table: "

Something went wrong

{"code":"ArgumentException","message":"Item '<ccon>XXXX</ccon>' already exists in the collection."}

Please check the technical details for more information. If you contact support, please provide these details."

- Trying to create a new relation:

{"code":"ArgumentException","message":"Item '<ccon>XXXX</ccon>' already exists in the collection."}

I also see "Stripes" on the top of my tables in the model view (I don't remember it was like that before my holidays)

Also, the date refreshed for all tables is the same, and is wrong (1/1/1, 12:09:21 AM).

Also a bug in pipelines: when I load data, and there is a problem with a NULL (by example if I try to load data with null in a column that don't accept null), it's not the good column name that is displayed in the error message ( I have seen that it happened few months ago in Synapse, seems like the same bug).

What is happening? Is it possible to have some help?

[Thayerthompson]

Hello. Have there been any resolutions to the issue of managing relationships in Data Warehouse model view? I'm receiving a similiar issue {"code":"ArgumentException","message":"Item '<ccon>XXXX</ccon>' already exists in the collection."}, a year after the original post. Thanks

[jisaac]

Was just running into this as well myself. Someone below said pressing "Automatically update semantic model" on the Data Warehouse should work, but that only gave me a different error. I "solved" it by just creating a "New semantic model" with my tables and working off of that. That might be the preferred way to do reporting anyway, not sure though.

[rash_user]

I was facing this same issue today but after updating my semantic model it got resolved. Give it a try.

[v-nikhilan-msft]

Hi @MylenePBI ,
Regarding the pipeline bug which you have mentioned, can you please provide more details regarding the error message. This would help me in understanding the issue better.
Thanks.

[v-nikhilan-msft]

Hi @MylenePBI 
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. Could you please provide more details regarding the error in pipelines?

Thanks

[MylenePBI]

Hello, I haven't tried today. The error was when I was trying to insert NULL data in a column that doesn't accept null. I was showing the good error, but not the good column name (for exemple the problem was happening on column BBB, but the message was saying that it was happening in column AAA).

[v-nikhilan-msft · Accepted solution]

Hi @MylenePBI ,
Thanks for the update.
Apologies for the issue you have been facing. The internal team has confirmed that there is an ongoing bug related to default dataset. This is the reason why you are getting an error when trying to manage the default dataset. The team is working to fix this issue ASAP.
I will keep you posted regarding the updates.
Appreciate your patience.

[Jerome22]

did you have some news on this issue?

I have the same problem.

I have multiple errors when trying to edit the default model.

the same issue: "Converting existing tables or partitions from Import or DirectQuery mode to Direct Lake is not supported."

when I try to add or remove any table from my model.

and another issue where I remove columns from a view and this cause any change to the model (like trying to add a measure) to fail because these columns are not longer there.

so I patched my view by adding the removed columns with a null value:

select ..., null as missingcolumnname from ...

so my columns are back and the model is not failing... but it's a problem.

[MylenePBI]

Hello, yes, the microsoft team is working on this issue, a fix should be available in december.

[arpost]

@v-nikhilan-msft, why was this marked as a solution if the issue is still happening?

[MylenePBI]

Hello, I was contacted by the Microsoft team yesterday. They have checked and confirmed the bug, and they will work on it. Currently there is no workaround. So there is nothing more to do, just wait...

[v-nikhilan-msft]

Hi @arpost ,
Our internal team got in touch with @MylenePBI  and confirmed that there are ongoing bugs related to this issue and will fix it ASAP. Hence I posted the same in the discussion and @MylenePBI accepted it.

Once I get updates from the internal team, I will inform here.
Thanks.

[v-nikhilan-msft]

Hi @MylenePBI ,

Thanks for the ask and using the Fabric Community.

At this time, we are reaching out to the internal team to get some help on this. We will update you once we hear back from them.
Thanks

[arpost]

Seeing the same issue. Can't create relationships between tables as it says "____ {Name of column being used as key between tables} already exists in this collection".

[AndyDDC]

In terms of the relationships issue, this has been encountered before and MS is actively looking into this.  In the meantime I suggest:

• Delete the relationships from the model view from the tables (so the table(s) has no relationships in the model view anymore)
• Run this SQL system query and see if you still see any FKs for that particular table

SELECT

    fk.name 'FK Name',

    tp.name 'Parent table',

    cp.name, cp.column_id,

    tr.name 'Refrenced table',

    cr.name, cr.column_id

FROM

    sys.foreign_keys fk

INNER JOIN

    sys.tables tp ON fk.parent_object_id = tp.object_id

INNER JOIN

    sys.tables tr ON fk.referenced_object_id = tr.object_id

INNER JOIN

    sys.foreign_key_columns fkc ON fkc.constraint_object_id = fk.object_id

INNER JOIN

    sys.columns cp ON fkc.parent_column_id = cp.column_id AND fkc.parent_object_id = cp.object_id

INNER JOIN

    sys.columns cr ON fkc.referenced_column_id = cr.column_id AND fkc.referenced_object_id = cr.object_id

ORDER BY

    tp.name, cp.column_id

• If you do, then delete the FK using SQL
  • ALTER TABLE <table_name> DROP CONSTRAINT <FK_Name>;
• Go back to the model view and create the relationships again and see if they now appear in the system tables

[arpost]

There are no keys as this is a new DW.

[AndyDDC]

Can you try creating the relataionships in the DW using SQL?

Primary, foreign, and unique keys - Microsoft Fabric | Microsoft Learn

[arpost]

I was able to create the PKs and FKs using SQL, but I can't change the cardinality in the data model view, so I'm stuck with One-to-Manys from my fact table to my Dim tables, when it should be the reverse. When I update, I get the same error (_____ already exists in this collection).