Microsoft Fabric existing connection Autodesk Construction Cloud not selectable in Dataflow Gen2

[floris_van_der_zwaard]

Hello,

We succesfully set up a new connection to Autodesk Construction Cloud and shared the connection with serveral users.

We can check the connection and it says that it is 'Online'.

According to the documentation this connection should be supported for Fabric Dataflow Gen2;

Autodesk Construction Cloud Power Query Connector - Power Query | Microsoft Learn

But when adding a Dataflow Gen2 and search for Autodesk Construction Cloud, the connection just will not show up. Also not after refreshing serveral times and retries after days.
See screenshot below;

Does anybode else have the same experience?

By the way:

The 'Sign in' is for signing in at Autodesk Construction Cloud, see screenshot below. That should come from the existing connection. That is the whole point of having a centralized Connection to Autodesk Construction Cloud. Or do I see this wrong?
We are in Europe, but I already tried the other 2 regions, just to be sure, the connection might come up there, but no luck!

 

After logging in with my Autodesk Construction Cloud account, it still does not show the existing connection to select. It does show a sort of placeholder; {"region":"Europe"} (none). See screenshot;

 

Link to same Post on Microsoft Fabric Community:

Existing Autodesk Construction Cloud connection no... - Microsoft Fabric Community

[floris_van_der_zwaard]

With the help of Microsoft support I found out the Autodesk Construction Cloud Connector can NOT be use this way in a Dataflow Gen2.

If you want to use a shared connection it has to be used in a Semantic Model.

It turns out the documentation is not correct on how this connector can be used.

The workaround is as follows.
After creating the connection as described, you have to create a PowerBi Desktop report, and set up a temporarily connection to Autdesk Construction Cloud in that report. Then publsh that report. This creates a semantic model in the workspace where the report is published.

In the setting of the Semantic model you can change the connection to the shared connection that was created before in the steps as described above.

Then in the same setting enable the option for OneLake ingegration. After a refresh of the semantic model, the semantic model will be available in OneLake. 

On top of that you could create a Lakehouse and create a link in the LakeHouse to the semantic model in the Onelake.