2 items
Choose classic or new designer for Power Automate flow/run URLs. Control survey flags. Reveal or enable Power Apps form elements. Stop Power Automate from opening the wrong designer and configure model-driven Power Apps forms your way. If you build on Microsoft Power Platform, small defaults add up. Flow links may not open the Power Automate designer you expect, while hidden or disabled controls on model-driven Power Apps forms can make configuration, testing, and support harder. Power Platform Configurator remembers and applies your choices in Google Chrome and compatible Microsoft Edge installations. What Power Platform Configurator does Power Automate — flow and run pages Choose your designer — Select Classic Designer or New Designer. Your preference is remembered and applied to supported Power Automate URLs whose path includes /flows/ or /runs/. See your mode at a glance — The toolbar icon displays C for Classic or N for New Designer. The badge is cleared when enforcement is Paused. Control the designer survey prompt — Choose Hide (default) to set v3survey=false when a supported URL is rewritten. Choose Show to normalize an existing v3survey parameter to true. Show does not add the parameter when it is absent. Pause without uninstalling — Paused disables URL changes and both declarative network rules while the extension remains installed. Power Apps — model-driven record forms Reveal hidden elements — On supported Dataverse organization URLs and apps.powerapps.com record forms, choose Reveal hidden elements to reveal hidden tabs, sections, and controls exposed by the form client API. Choose Keep hidden to stop automatic revealing. Enable disabled controls — Choose Enable disabled controls to enable controls exposed as disabled by the form client API. Choose Keep disabled to stop automatic enabling. Preferences remain active — Power Apps choices are stored in browser sync and reapplied after completed tab loads, preference changes, popup requests, browser Back/Forward navigation, and URL changes detected by a short-lived startup watchdog. A late same-document record change may require reloading the page. After selecting Keep hidden or Keep disabled, reload open forms to restore their platform-defined state. Elements removed in the form designer cannot be revealed. Field-level security and platform scripts may keep controls disabled or prevent saving. Canvas apps, list views, dashboards, and maker portals are not supported. Popup and preferences The toolbar popup contains Power Automate, Power Apps, and About tabs. Designer, survey, and Power Apps preferences use browser sync. The popup Light or Dark appearance setting is stored only on the current device. Who it is for Power Automate authors, makers, and administrators who want predictable designer behavior, and Power Apps consultants, developers, testers, and support users who need to inspect or configure supported model-driven record forms. How it works On permitted Power Automate hosts, the extension adjusts flow and run URLs so the v3 parameter matches the selected designer. It optionally adjusts v3survey according to the Hide or Show setting. Enforcement uses declarative network rules, background navigation checks, and lightweight in-page checks. On permitted Power Apps hosts, the extension injects a packaged, self-contained function that uses the standard Xrm form client API while Reveal hidden elements or Enable disabled controls is active. The extension does not load remote code, transmit URLs or form content to Helvety, collect analytics, or run on websites outside its declared Microsoft Power Platform host permissions. Before you install Microsoft can change Power Automate URLs, designer behavior, and Power Apps form APIs. After installation, open a supported flow or run page and a model-driven record form, choose your preferences in the popup, and verify the expected behavior. If a form is still loading or you navigate between records without a full page load, reload the page once.
Jul 19, 2026
rating_count is the Chrome Web Store ratings count, not a written-review count.
Media assets
Screenshots and videos on the listing.
Has promo video
Whether the listing includes at least one video.
Languages
Declared language locales.
Developer website
Listing exposes a developer website URL.
Contact email
Listing exposes a contact email.
Keyword in name
Case-insensitive substring match in the name.
Keyword in description
Case-insensitive substring match in the description.
Keyword occurrences in description
Count of case-insensitive occurrences in the description.
Category user-count percentile
Share of same-category extensions with fewer users (null if unknown).
These are transparent listing completeness / keyword signals, not a prediction of Chrome Web Store search ranking.