Forum Discussion
Business Card Reader in mixed Dynamics 365 & Power Apps licensing Estate
The business card reader in Sales Enterprise uses the app's camera controls (on mobile) or an image of the business card (on desktop) to automatically process fields from the business card.
With Sales Enterprise, you actually get 10 scans per user per month, pooled at the TENANT level which means that in a 10 user setting you actually get 100 scans but you could end up in a situation where 1 person scans 90 leaving the other 9 individuals with only 10 scans left.
The business card reader functionality within AI builder is a different, separate thing and in no way related to the functionality in Sales Enterprise. Here you'll use a custom app with a back-end process linked to Power Automate/AI Builder and perform a similar function but within the Power App itself and not within the Sales Enterprise application. AI Builder should be able to extract the necessary, relevant text and create what I'd assume to be "Leads" in CRM since Leads isn't a restricted table. When users are using the custom app linked to AI Builder, they will be subject to AI Builder credits. When they are using the business card reader functionality in CRM, they will be subject to those limitations.
It's really simple - don't over think it.
blakecheek thanks for the response. I have to say, though, our investigation shows that the Business Card Reader in Sales Enterprise is the same component as the one you would use in your custom Power App - i.e., the AI Builder component.
If we look at the Lead Quick Create form in the Sales Hub app, you can see it's the AI Builder Business Card control, as per this screenshot:
The control behaves slightly differently than it does completely out of the box, but this seems to be because of a very clever Javascript library on the form. Therefore, we surmised that the Javascript is the "Sales Enterprise" app part, and the BCR component is the standard AI Builder one.
This is the basis of the question we're asking. It clearly is the AI Builder component that the Dynamics app is using, ergo it seems reasonable that once the pool of available scans from Dynamics 365 Sales Enterprise runs out, users should still be able to use the functionality (maybe without the fancy Javascript) with spare AI Builder credits.
- Think of it like this:
D365 user does business card reader from within D365 -> it will deduct from D365 entitlement
D365 user does business card reader from custom app connected to AI Builder -> it will deduct from AI Builder credits.
If you're looking to use the same business card reader in D365 and hoping that it starts deducting from your AI Builder credits once your D365 entitled credits run out, I don't think it works that way.
Separate apps = separate buckets, imo.
At the same time, I have to wonder what kind of industry still has massive volumes of business cards that they need to scan in 2023? Anything more than a couple hundred seems egregious.- Lol - I certainly agree with the last part, but you know customers! We have a prospective customer who is getting very hung up on this. To be fair, our customers do a lot of in-person networking.
One thing we've always struggled with a little in our customer base is what constitutes "being in D365". All our users use a custom app anyway, even those with D365 SE licenses, so maybe none of them would be classed as being in D365.
