microsoft / microsoft/Dynamics-365-FastTrack-Implementation-Assets
Can read manifest data in CDMUtil_ConsoleApp, but not CDMUtil_AzureFunction
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 494
- Forks
- 296
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 5
Description
Folks,
Thanks so much for building this utility!
I'm able to use the console app to connect to our storage account and read manifests, however, I'm not able to do the same with the AzureFunction.
We are not using the EventGrid_CDMToSynapseView function, as we are connecting to a private endpoint, so as suggested by Microsoft, we are using a Service Bus Trigger instead (https://docs.microsoft.com/en-us/azure/event-grid/consume-private-endpoints#deliver-events-to-service-bus-using-managed-identity).
I've created a custom function, ServiceBusQueueTriggerPL, in my fork (https://github.com/princeton-lau/Dynamics-365-FastTrack-Implementation-Assets) that essentially does the same thing as the EventGrid one... it deploys fine and runs up until it attempts to read the manifest, and that is when it throws these errors:

I ran the console app with the same tenantid, accesskey, manifestURL and DB connection string and it reads the manifest just fine. I dumped out the parameters to the ManifestReader constructor and the values for both apps were the same:

I've added log statements to troubleshoot the exact line of code, 136, that fails in the ManifestHandler.cs class:

Is there a procedure I need to follow to get the AzureFunction to work?
Thanks!
Princeton
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with ManifestHandler.cs at the reported failing line 136, then compare how CDMUtil_ConsoleApp and CDMUtil_AzureFunction construct and use ManifestReader. Review the custom ServiceBusQueueTriggerPL entry point and its Azure Function configuration. Done means the Azure Function can read the manifest using the same parameters as the console app.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, csharp
- Domain
- backend, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100