This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreDid you hear? There's a new SQL AI Developer certification (DP-800). Start preparing now and be one of the first to get certified. Register now
Hello all,
I added a new field named fabric test into Custtable. After adding that I refreshed the fabric tables in power apps using Azure synapse link selecting the custtable. As per microsoft documentation with the refresh fabric tables in power apps through Azure synapse link the meta data will get refreshed and we see all the fields in Fabric lakehouse. But my custom field is not visible in the lakehouse even after following the documentation.
Attaching the image of the documentation.
1. What do I do now to make that field available in fabric?
2. I tried refereshing the semantic model and that semantic model has the custtable in it this also didn't workout
Any suggestions are highly appreciated!
Solved! Go to Solution.
Hi @Ramkishor ,
Thanks for the detailed explanation and the screenshot from the docs — that helps a lot.
So, even though you followed the documented steps and refreshed the Fabric tables via Synapse Link, your custom field still isn’t showing up in the Lakehouse. That’s frustrating, but here are a few things you can try that usually help in this kind of situation:
Make sure the field is enabled for change tracking in Dataverse
If the field isn’t tracked, it might not be included in the sync even after refreshing.
Reopen the Synapse Link settings in Power Apps
Go to make.powerapps.com → Synapse Link → your link profile → check if the new field is actually selected under the CustTable. Sometimes new fields are not auto-selected.
Try removing and re-adding the CustTable from the link
This forces a full metadata refresh and can help when incremental updates don’t pick up schema changes.
Check the Lakehouse schema directly
In Fabric, open the Lakehouse and inspect the CustTable schema. Sometimes the field is already there in the backend but not yet reflected in the semantic model.
Refresh the semantic model again
Even though you already tried this, do it once more after verifying the field is selected in Synapse Link. Also, try clearing the cache in Power BI Desktop if you're using it to view the model.
If none of these work, it might be a backend sync delay or a bug — in that case, opening a support ticket could be the best next step.
If my response resolved your query, kindly mark it as the Accepted Solution to assist others. Additionally, I would be grateful for a 'Kudos' if you found my response helpful.
translation and text editing supported by AI
Hi @Ramkishor,
May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.
If we don’t hear back, we’ll go ahead and close this thread. For any further discussions or questions, please start a new thread in the Microsoft Fabric Community Forum we’ll be happy to assist.
Thank you for being part of the Microsoft Fabric Community.
Hi @Ramkishor ,
We would like to follow up to see if the solution provided by the super user resolved your issue. Please let us know if you need any further assistance.
@burakkaragoz , thanks for your prompt response.
Thanks,
Prashanth Are
MS Fabric community support
If our super user response resolved your issue, please mark it as "Accept as solution" and click "Yes" if you found it helpful.
Hi @Ramkishor,
We would like to follow up to see if the solution provided by the super user resolved your issue. Please let us know if you need any further assistance.
@burakkaragoz , thanks for your prompt response.
Thanks,
Prashanth Are
MS Fabric community support
If our super user response resolved your issue, please mark it as "Accept as solution" and click "Yes" if you found it helpful.
Hi @Ramkishor ,
Thanks for the detailed explanation and the screenshot from the docs — that helps a lot.
So, even though you followed the documented steps and refreshed the Fabric tables via Synapse Link, your custom field still isn’t showing up in the Lakehouse. That’s frustrating, but here are a few things you can try that usually help in this kind of situation:
Make sure the field is enabled for change tracking in Dataverse
If the field isn’t tracked, it might not be included in the sync even after refreshing.
Reopen the Synapse Link settings in Power Apps
Go to make.powerapps.com → Synapse Link → your link profile → check if the new field is actually selected under the CustTable. Sometimes new fields are not auto-selected.
Try removing and re-adding the CustTable from the link
This forces a full metadata refresh and can help when incremental updates don’t pick up schema changes.
Check the Lakehouse schema directly
In Fabric, open the Lakehouse and inspect the CustTable schema. Sometimes the field is already there in the backend but not yet reflected in the semantic model.
Refresh the semantic model again
Even though you already tried this, do it once more after verifying the field is selected in Synapse Link. Also, try clearing the cache in Power BI Desktop if you're using it to view the model.
If none of these work, it might be a backend sync delay or a bug — in that case, opening a support ticket could be the best next step.
If my response resolved your query, kindly mark it as the Accepted Solution to assist others. Additionally, I would be grateful for a 'Kudos' if you found my response helpful.
translation and text editing supported by AI
Check out the April 2026 Fabric update to learn about new features.
Sign up to receive a private message when registration opens and key events begin.
| User | Count |
|---|---|
| 35 | |
| 19 | |
| 13 | |
| 11 | |
| 10 |