Notes for PL 200 : Receipt Processing in AI Builder

Important points for Exam:

  1.   Receipt Processing lets read and save key information from common Sales receipts, such as receipts that are used in restaurants, gas stations, retails and more.
  2. The prebuilt AI model uses state- of art optical character recognition (OCR) to extract printed and hand written text receipts. such as merchant details, transaction date and time, a list of purchased items, taxes and total.
  3. No training or Prior configuration is required to use receipt processing.
  4. It only needs to provide an image or a PDF file and the model will instantly return the results.
  5. Only English receipts from the United States are correctly supported. full page receipts, such as hotel receipts or invoices are not supported
  6. Common business problems that can be solved with receipt processing include:-
    • Travel and Expense  (T & E)
    • Accounting and Auditing


Comments

Post a Comment

Popular posts from this blog

Dynamics 365 Plugin Life Cycle Simplified for Business Users and Developers

Image
The Dynamics 365 Plugin Life Cycle describes the series of steps that a plugin follows when a record is created, updated, deleted, or otherwise changed in Dataverse. In simple terms, a plugin is like an automated rule that wakes up when something happens in the system. As the event occurs, the plugin passes through different pipeline stages— Pre-Validation, Pre-Operation, Post-Operation, and Asynchronous Processing —each with its own purpose. Pre-Validation allows very early checks before the system applies business rules, Pre-Operation lets you validate or modify data before it is saved, Post-Operation triggers after the record is committed to the database, and Async handles background tasks like integrations or long-running operations. Understanding this life cycle helps ensure business logic runs at the right moment, prevents bad data from entering the system, and enables smooth automation and integrations within Dynamics 365. Plugins in Dynamics 365 are pieces of custom code that ...
Read more

Decode and Fix: “This Data Type is Unsupported for Evaluation” in Power Apps

Image
 One common frustration when building Canvas Apps over Dataverse is encountering this cryptic error:  “This data type is unsupported for evaluation” This message typically appears when Power Apps cannot process or render a specific Dataverse column type within a control or formula. While it may seem vague, it’s usually tied to specific patterns involving complex column types or runtime data structure mismatches. In this blog, we'll explore common causes, scenarios, and practical fixes from both a developer and architectural standpoint. Root Causes of the Error 1. Polymorphic Lookups Dataverse supports polymorphic relationships (e.g., `Owner`, `Customer`, `Regarding`) that can point to multiple entity types. These lookups can't be directly evaluated in Power Apps unless you cast the reference explicitly. Use: If(     IsType(ThisItem.Customer, Account),     AsType(ThisItem.Customer, Account).Name,     AsType(ThisItem.Customer, Contact).FullName ) 2....
Read more

Managing Parallel Development and Hotfixes in Dataverse Like a Pro

Image
Managing parallel development and hotfixes in Dataverse means keeping new features and urgent fixe s moving forward at the same time without breaking the system. Because multiple teams often work in different solution layers , it becomes important to separate work clearly using branching, small modular solutions, and structured environments. While feature teams work on future releases in their own branches, hotfixes must be created quickly from the production branch, packaged in focused solutions, tested, and deployed with minimal impact. After a hotfix goes live, it must always be merged back into the development stream so it isn’t overwritten in the next release. With a good CI/CD pipeline, versioning, and clear release governance, organizations can deliver changes safely, avoid solution conflicts, and maintain stability even when several teams are building and fixing at the same time. Working with Dataverse often means several developers, consultants, and teams are customizing the...
Read more

Plugin Trace Logs in Dataverse Explained: Debug Smarter, Not Harder

Image
Plugin Trace Logs in Dataverse are a built-in logging mechanism that help developers understand what happens inside a plugin while it is running. They capture detailed runtime information such as execution steps, input and output parameters, custom trace messages, execution depth, user context, and any exceptions thrown by the plugin. This is especially important because Dataverse plugins run on the server, where traditional debugging tools like breakpoints are not available in production. By using plugin trace logs, developers can safely trace execution flow, identify where and why failures occur, analyze performance issues, and validate business logic without impacting users. Overall, Plugin Trace Logs are essential for reliable plugin development, faster troubleshooting, and maintaining stable, production-ready Dynamics 365 and Power Platform solutions . Plugin Trace Logs = Black Box Recorder for Dataverse Plugins What are Plugin Trace Logs? Plugin Trace Logs are diagnostic logs ge...
Read more

Microsoft Dynamics 365 Customer Experience Analyst : Configure connections and connection roles

Image
In Microsoft Dataverse, connections and connection roles are used to define and manage relationships between records across different tables. A connection allows you to link two records (for example, an account and a contact, or a case and a user) without creating a custom relationship. Each connection can have roles assigned to both sides, called connection roles , which describe the nature of the relationship (such as Account Manager – Customer, Employee – Employer, or Consultant – Client). This makes connections very flexible for modeling real-world interactions where multiple entities need to be related in different contexts. By leveraging connections and connection roles, organizations can track not just the data itself but also the context of how people, accounts, and activities are linked, improving collaboration and providing a 360-degree view of relationships in Dataverse. What are Connections  in Dataverse? A Connection   is a flexible way to represent a  ...
Read more

Architecting Scalable Business Logic in Dynamics CRM Using Plugin Life Cycle

Image
Dynamics CRM Plugin Life Cycle: Optimizing for Scalability means designing plugins in a way that keeps the system fast, stable, and easy to maintain—even as the business grows. A plugin goes through a clear life cycle: it triggers when data changes, runs inside the Dataverse execution pipeline, processes business logic, and returns results. For architects, the goal is to place the right logic in the right stage, avoid heavy or unnecessary operations, and use asynchronous processing whenever possible to reduce load on the user experience. By using best practices—such as separating business logic into helper classes, minimizing database calls, handling errors safely, and avoiding infinite loops—architects can ensure plugins scale smoothly across high-volume scenarios. In simple terms, it’s about building plugins that can handle more data, more users, and more transactions without slowing down the CRM system. When you design plugins in Dynamics 365, you’re not just writing C# code — you’...
Read more

Step-by-Step Guide to Building Custom APIs in Dataverse

Image
Custom APIs in Microsoft Dataverse allow developers and architects to create their own reusable, secure, and well-defined service endpoints that extend the standard Dataverse Web API. Instead of relying solely on out-of-the-box messages (like Create, Update, or Retrieve ), Custom APIs let you define your own business operations — complete with input and output parameters — that encapsulate complex logic and can be called from Power Automate, Power Apps, or external systems. These APIs are registered once and behave like native Dataverse operations, making them ideal for implementing domain-specific logic, integrating with external services, or simplifying client-side development. From a technical standpoint, a Custom API can be implemented through a plugin class, where the backend logic is written in C#. Developers can control security through privilege definitions and ensure consistency by centralizing key business rules. Custom APIs are particularly valuable in enterprise environmen...
Read more

Designing Secure Power Platform Solutions with Dataverse Security Roles

Image
Understanding Dataverse Security Roles is essential for anyone working with Microsoft Power Platform and Dynamics 365—whether you are a business user, system administrator, or developer. Security roles define who can see what and do what within Dataverse by controlling access to data, actions, and system capabilities. For business users, they ensure day-to-day work is simple and secure without exposing sensitive information. For administrators, security roles provide a structured way to enforce organizational policies, compliance, and separation of duties. For developers, they are critical to designing solutions, plugins, and integrations that respect data boundaries and avoid unintended access. A well-designed security role model balances usability, performance, and compliance, ensuring the right people have the right access at the right time—no more, no less. Dataverse security is not about restriction — it’s about trust, clarity, and control. Dataverse security roles control who ca...
Read more

Decode & Fix : Shared App host initialization has timed out in Microsoft Power Apps

Image
  Issue : While working with apps in the Microsoft Power Platform, we encountered a critical issue where the application failed to load properly. This error appeared intermittently, especially when using custom pages and embedded components. Shared App host initialization has timed out Error Log :  Shared App host initialization has timed out UciError: Shared App host initialization has timed out at s (https://content.powerapps.com/resource/uci-infra-web/scripts/app.4e71963626213ae9901b5ff59d931193.js:38:222131) at Object.execute (https://content.powerapps.com/resource/uci-infra-web/scripts/mds.ca217cfe2bc4dbe9b337ff1da6ed7c28.js:4:9805) at https://content.powerapps.com/resource/uci-infra-web/scripts/app.4e71963626213ae9901b5ff59d931193.js:14:669926 at new Promise (<anonymous>) at w._executeAsyncAction (https://content.powerapps.com/resource/uci-infra-web/scripts/app.4e71963626213ae9901b5ff59d931193.js:14:669627) at w._executeAsync (https://content.powerapps.com/resour...
Read more

Dataverse Integration Patterns: Sync vs Async vs Event-driven (Real Use Cases)

Image
As organizations start using Microsoft Power Platform, Microsoft Dataverse is no longer just a place to store data—it becomes a key part of how systems connect and work together. For IT professionals and developers with experience in traditional integration, this often brings up important questions: Should the integration happen in real time (synchronous) or in the background (asynchronous)? When should we use event-driven design? How will these choices affect performance, reliability, and scalability? Dataverse supports different integration approaches, such as: Real-time API calls (synchronous) Background processing (asynchronous) Event-driven integrations using messaging and automation tools Each approach has its own purpose and trade-offs. Choosing the right one is important, because the wrong choice can lead to slow performance, unstable integrations, or limitations in the system. Why Integration Patterns Matter in Dataverse (Before Choosing Tools) When working with Microsoft Data...
Read more