Extracting Data from Legacy Desktop Apps with Power Automate
You are developing a Power Automate desktop flow to process thousands of product data sheets. The data sheets reside in an older desktop application. Each data sheet is the same format and contains a product image and description field. You need to extract the product image and description from each product sheet and add those elements to a table in Microsoft Dataverse. Which two Power Automate Desktop automation capabilities should you use? Each correct answer presents complete solution. NOTE: Each correct selection is worth one point.
Community Votes
100% of anonymous learners picked answer CE. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
Tests the distinction between native UI extraction and optical character recognition (OCR) when dealing with non-standard or image-bound data formats in older applications.
This question addresses extracting product images and descriptions from a legacy desktop application into Dataverse. It establishes that OCR is required for image-based text while UI element details are needed for standard fields.
Candidates often select 'Change focus' or 'Wait for window', which are control actions rather than data extraction methods, failing to address the specific need to capture content.
Community Discussion (4 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
The scenario involves a legacy application where data might be rendered as an image or requires robust text extraction capabilities. Option E (Extract text by using OCR) is essential because it allows the automation to read text from screenshots or embedded images within the application, covering the description field if it's not natively selectable. Option C (Get UI element details) is the complementary action needed to extract structured data from standard UI controls, ensuring both the image reference and any accessible text fields are captured accurately for the Dataverse table.Why the Other Options Are Wrong
Option A (Change the focus) and Option B (Wait for window content) are workflow control actions used to navigate or synchronize timing, not to extract data values. Option D (Capture an image) only saves a screenshot to disk; it does not process or extract the underlying data (text or metadata) required to populate the Dataverse table fields.Community Comment Notes
Community consensus strongly favors C and E. As MotherOfHarryPotter noted, "Since the description field is in an image. Need OCR to extract," highlighting the necessity of OCR for image-bound text. Another user, sugaSri, explained that C extracts specific UI data while E handles image-based text, providing a complete solution for both elements.Exam Strategy
When asked about data extraction from legacy apps, always look for OCR if images are involved. Pair OCR with native UI extraction actions (like Get UI Element Details) to ensure you can handle both structured and unstructured data sources effectively.
Frequently Asked Questions
Why can't I just use Capture an Image?
Capturing an image only saves a visual snapshot. It does not extract the actual text or data values needed to populate the Dataverse table fields.
When should I use OCR vs Get UI Element Details?
Use Get UI Element Details for standard, selectable text fields. Use OCR when the text is part of an image or rendered in a way that prevents direct selection.