Unanswered

Azure Synapse Link fails to create model.json

(0) Share

Report

Posted on by nebarnes

Hi, I am trying to create a new Azure Synapse Link but the model.json file is empty and the OptionSetMetadata folder is not created.

I was able to create a link on 16th January but due to an unrelated issue, we had to unlink and start from scratch. I am now trying to recreate the link but am having issues with an empty model.json file and no OptionSetMetadata folder.

I have set the advanced options to incremental, chosen a suitable timeframe and selected all of my tables in the Power Apps menu, just as I did on Monday. The link is created correctly and a container is generated on our storage account. All of the selected tables are downloaded to the container correctly.

However, the model.json file is never populated and the OptionSetMetadata folder and associated CSVs are missing, meaning we are unable to process the data with Azure Data Factory.

We havent changed anything about our setup, other than unlinking the original config. Is there an issue with deploying new links?

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (5)

Answers (0)

HamidBee 932 Super User 2024 Season 1 on at

Like (0)

Report

Hi, I am trying to create a new Azure Synapse Link but the model.json file is empty and the OptionSetMetadata folder is not created.

I was able to create a link on 16th January but due to an unrelated issue, we had to unlink and start from scratch. I am now trying to recreate the link but am having issues with an empty model.json file and no OptionSetMetadata folder.

I have set the advanced options to incremental, chosen a suitable timeframe and selected all of my tables in the Power Apps menu, just as I did on Monday. The link is created correctly and a container is generated on our storage account. All of the selected tables are downloaded to the container correctly.

However, the model.json file is never populated and the OptionSetMetadata folder and associated CSVs are missing, meaning we are unable to process the data with Azure Data Factory.

We havent changed anything about our setup, other than unlinking the original config. Is there an issue with deploying new links?

If my reply helped you, please give a 👍, & if it solved your issue, please 👍& Accept it as the Solution to help other community members find it more.

Was this reply helpful? Yes No
nebarnes 6 on at

Like (0)

Report

I tried creating another link on Saturday morning and left it over the weekend. Still no OptionSetMetadata folder, and still an empty model.json file. No incremental folders have been added to our Azure Blob Storage account either, despite several time increments passing since it was created.

It downloaded the initial batch of data and has done nothing else - I've checked Power Apps and can confirm that multiple tables and records have received changes since creating the new link.

Was this reply helpful? Yes No
BritonWells 2 on at

Like (0)

Report

Running into this as well. Ran into some issues when adding/removing columns to a table which seemed to cause an error so dropped the link.

After re-linking, tables were quickly recreated in ADLS but with an empty model.json and no OptionSetMetadata folder. Everything on the power platform side says Active. Only 11 tables and most only have <100 records.

I have also tested creating a brand new, empty storage account (ADLS) and creating a link there - same behavior

Was this reply helpful? Yes No
nebarnes 6 on at

Like (1)

Report

Hey, I ended up having to raise a support ticket which eventually ended up with the engineering team. I kept deleting the link and recreating it every few days and it eventually just started working randomly about a week later. When my ticket was finally answered, they could see a fault happened, but I no longer needed their help. Log a ticket and see if you get a speedier response!

Support | Microsoft Power Apps

Was this reply helpful? Yes No
BritonWellsLVS 19 on at

Like (0)

Report

Good to know - actually we had the model.json start to populate all of a sudden as well. For now we are just in development so wasn't critical

Was this reply helpful? Yes No