Announcements
I've spent several days trying to find a clean way of indexing some dataverse tables with Cognitive Search through Synapse Link but have hit several brick walls that leads me to conclude there's probably a better way of doing this. The biggest hurdle I have is getting Cognitive Search to work with a Serverless SQL Pool, which in itself isn't a Power Apps problem but thought I'd share here in case anyone is attempting something similar. Cognitive Search could enable much more powerful search experiences to be built within Power Apps so it's a **bleep** shame it doesn't just work "out-of-the-box". I have a couple of outstanding Q&As with Microsoft which may get me a step closer but I'm not holding my breath.
Fabric Shortcuts for Dataverse data were just announced this week at MPPC. If the demo is to be believed, it will dramatically simplify data analytics and processing of all kinds. You can sign up for the preview here:
https://learn.microsoft.com/en-us/power-apps/maker/data-platform/azure-synapse-link-view-in-fabric
Thanks for the info @cchannon. Wouldn't it be nice if MS actually tested something before releasing it in the wild?! I get that it's still in Preview but leaving test copy in labels doesn't inspire me with confidence...
Jokes aside, I've tried in vain to add tables to the OneLake connector. If I click Manage tables then select a few and click Save, it just returns me back to the message "No tables have been enabled for this link".
Even if I were able to get this to work, I'm not sure it'll get me any closer to having the data indexed by Cognitive Search, since for now there's no option to create a Cognitive Search datasource from OneLake:
I live in hope!
Well that's disappointing, but hopefully will be updated soon. In the meantime I guess you're stuck slogging through with ADLS g2. So what's the piece that has you using SQL? Why not just point Cog Search at ADLS directly?
The tables I want to index have some complex relationships (1:n and n:n) and I thought the best way of denormalizing the data for the index was with a SQL query. Perhaps the only way around this is using Data Factory and a dedicated SQL.
Yeah, the Data Factory connector for Data Lake can natively re-link to the metadata, which right away is going to make your life MUCH easier.
https://learn.microsoft.com/en-us/azure/data-factory/connector-dynamics-crm-office-365?tabs=data-factory#create-a-linked-service-to-dynamics-365-microsoft-dataverse-or-dynamics-crm-using-ui
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
Jump in, show your community spirit, and win prizes!
Expanding mentorship, skilling, and AI innovation
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Valantis 474
WarrenBelz 375 Most Valuable Professional
