Q: 2
You are a sales manager for a large retail organization.
You are creating a Power Apps app that will display customer product purchase information from
your old point-of-sale (POS) system and need to link those sales to the customer accounts and
product sales in Dynamics 365 Commerce.
You need to use the appropriate component.
What should you use?
Options
Discussion
I don’t think D is right here. Option C (Common Data Service) is designed for integrating and relating data across systems like POS and D365, while entity metadata (D) just defines structure. Fairly confident in C but open to other angles if I’m missing something.
C that's the right move here.
C imo. Common Data Service is made to pull together data from different sources, which you need for linking POS and Dynamics 365. Official docs and practice questions usually stick with C for this scenario.
Ugh, Microsoft changes the name to Dataverse and expects us to keep up. C is what you want here. It's the backbone for bringing in external data and relating it to Dynamics stuff, way more suitable than business rules or process flows for linking POS sales with Commerce accounts. Pretty sure on this one, unless MS licensing trips us up somewhere.
I think C. Official docs and some practice questions point to Common Data Service (now Dataverse) for integrating legacy data with Dynamics apps.
Probably C, since connecting data between old and new systems in Power Apps usually means using Common Data Service (Dataverse).
D feels tricky but I'm pretty sure it's C here, since entity metadata (D) just handles structure, not integration.
C , entity metadata (D) just sets the schema but doesn't actually link or integrate your POS data with Dynamics 365 Commerce. Practice and exam reports both steer toward C for scenarios like this. Anyone see a reason D would work better?
Probably C for this. Common Data Service is exactly what you want when integrating data sources and making sure Power Apps can access and relate the records from both the old POS and Dynamics 365. Not 100% sure if there's a weird edge case, but everything in the docs points to C.
Actually, I'd pick D here. Entity metadata is what controls schema linking, right? C feels like a trap option to me.
Be respectful. No spam.
