web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Apps / How can I access Datav...
Power Apps
Suggested Answer

How can I access Dataverse Environment Variables from my PCF component? Any practical use cases?

(2) ShareShare
ReportReport
Posted on by 1

Hi everyone! 👋

I'm new in PCF developement

I'm working on a PCF (PowerApps Component Framework) control and I'm wondering how I can read Dataverse Environment Variables directly from my component


  • Is there an officially supported way to access them within a PCF?

  • Can this be done securely and efficiently at runtime?

  • If you've used this in your own projects, could you share a real use case or example where it helped you avoid hardcoding or made your component more flexible

I’d really appreciate any guidance or examples. Thanks in advance! 🙏

 

 

here is my PCF : 

import { IInputs, IOutputs } from "./generated/ManifestTypes";
import * as React from 'react';
import { Component } from "./Component";
import * as ReactDOM from 'react-dom/client';


 
export class FileUpload implements ComponentFramework.StandardControl<IInputs, IOutputs> {
    private _container: HTMLDivElement;
    private _root: ReactDOM.Root | undefined;
 
    /**
     * Empty constructor.
     */
    constructor() {
        // Empty
    }
 
    /**
     * Used to initialize the control instance. Controls can kick off remote server calls and other initialization actions here.
     * Data-set values are not initialized here, use updateView.
     * @param context The entire property bag available to control via Context Object; It contains values as set up by the customizer mapped to property names defined in the manifest, as well as utility functions.
     * @param notifyOutputChanged A callback method to alert the framework that the control has new outputs ready to be retrieved asynchronously.
     * @param state A piece of data that persists in one session for a single user. Can be set at any point in a controls life cycle by calling 'setControlState' in the Mode interface.
     * @param container If a control is marked control-type='standard', it will receive an empty div element within which it can render its content.
     */
    public init(
        context: ComponentFramework.Context<IInputs>,
        notifyOutputChanged: () => void,
        state: ComponentFramework.Dictionary,
        container: HTMLDivElement,
       
    ): void {
        this._container = container;
 
       }
 
   
   
    /**
     * Called when any value in the property bag has changed. This includes field values, data-sets, global values such as container height and width, offline status, control metadata values such as label, visible, etc.
     * @param context The entire property bag available to control via Context Object; It contains values as set up by the customizer mapped to names defined in the manifest, as well as utility functions
     */
    public updateView(context: ComponentFramework.Context<IInputs>): void {
        if (!this._root) {
            this._root = ReactDOM.createRoot(this._container);
        }
       
        this._root.render(
            React.createElement(Component, { context })
        );
    }
   
   
 
    /**
     * It is called by the framework prior to a control receiving new data.
     * @returns an object based on nomenclature defined in manifest, expecting object[s] for property marked as "bound" or "output"
     */
    public getOutputs(): IOutputs {
        return {};
    }
 
    /**
     * Called when the control is to be removed from the DOM tree. Controls should use this call for cleanup.
     * i.e. cancelling any pending remote calls, removing listeners, etc.
     */
    public destroy(): void {
            // no cleanup necessary
    }
}
I have the same question (0)
  • Suggested answer
    Michael E. Gernaey Profile Picture
    53,963 Moderator on at
     
     
    But also, adding input properties to your PCF where you can pass them in from within the Model or Canvas or Pages works great.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the May Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Apps

#1
Valantis Profile Picture

Valantis 413

#2
WarrenBelz Profile Picture

WarrenBelz 355 Most Valuable Professional

#3
timl Profile Picture

timl 315 Super User 2026 Season 1

Last 30 days Overall leaderboard