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

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics 365 | Integration, Dataverse...
Suggested Answer

PCF does not load via browser refresh

(4) ShareShare
ReportReport
Posted on by 8
I am trying out creating PCF controls. I have made a PCF that displays the color of Choice values. 
 
When opening a record it displays the data fine (with color):
  
 
  
When I use the refresh button within the model driven app, the PCF loads correctly, but when I refresh the record via the browser refresh (I use Google Chrome), the PCF does not load:
 
 
I believe the reason is, that the PCF loads before the values of the Choice is populated, but I'm not sure.
 
Do you know how I make the PCF responsive to the browser refresh?
 
This is the index.tx file:
 
 
 
import { IInputs, IOutputs } from "./generated/ManifestTypes";

 
 
export class JejorTestPcf implements ComponentFramework.StandardControl<IInputs, IOutputs> {

 
 
    /**
 
     * Empty constructor.
 
     */
 
    private _inputElement: HTMLInputElement;

 
 
    private _dropdownElement: HTMLSelectElement;
 
    private _notifyOutputChanged: () => void;
 
    private _options: ComponentFramework.PropertyHelper.OptionMetadata[] = [];

 
 
    constructor()
 
    {

 
 
    }

 
 
    /**
 
     * 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._dropdownElement = document.createElement("select") as HTMLSelectElement;
 
        this._options = context.parameters.sampleProperty.attributes?.Options || []; // Get options from manifest

 
 
        // Set default dropdown styles
 
        this._dropdownElement.style.color = "#000000";
 
        this._dropdownElement.style.backgroundColor = ""; // Default white background

 
 
        // Ensure the initial value is set correctly
 
        if (context.parameters.sampleProperty.raw !== null && context.parameters.sampleProperty.raw !== undefined) {
 
            const initialOption = this._options.find(option => option.Value === context.parameters.sampleProperty.raw);
 
            const initialColor = initialOption?.Color || "";
 
            this._dropdownElement.style.backgroundColor = initialColor;
 
        }

 
 
        // Loop start
 
        this._options.forEach(option => {
 
            const optionElement = document.createElement("option");
 
            optionElement.value = option.Value.toString(); // Saves number value
 
            optionElement.text = option.Label; // Shows readable text
 
            if (option.Color) {
 
                optionElement.style.backgroundColor = option.Color;} // Apply color if available
 
            this._dropdownElement.appendChild(optionElement); // Append option to dropdown
 
        });
 
        // Loop end
 
       
 
        container.appendChild(this._dropdownElement); // Append dropdown to container

 
 
        // Eventlistener start
 
        this._dropdownElement.addEventListener("change", () => {
 
            const selectedOption = this._options.find(option => option.Value.toString() === this._dropdownElement.value); // Find selected option
 
            const selectedColor = selectedOption?.Color || ""; // Default to white if no color is set
 
            this._dropdownElement.style.backgroundColor = selectedColor; // Set the background color
 
            this._dropdownElement.style.color = "#000000"; // Ensure text is visible
 
            notifyOutputChanged();
 
        });
 
        // Eventlistener end
 
       
 
    }

 
 
    /**
 
     * 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
 
    {
 
        // Add code to update control view
 
        this._dropdownElement.value = context.parameters.sampleProperty.raw?.toString() || '';
 
       
 
    }

 
 
    /**
 
     * 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 {
 
            sampleProperty: this._dropdownElement.value ? Number(this._dropdownElement.value) : undefined

 
 
        };
 
    }

 
 
    /**
 
     * 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
 
    {
 
        // Add code to cleanup control if necessary
 
    }
 
}
 
 
 
 
 
 
 

 
Categories:
I have the same question (0)
  • Suggested answer
    Holly Huffman Profile Picture
    6,538 Super User 2025 Season 2 on at
    Good morning, afternoon, or evening depending on your location!
     
    This behavior is often influenced by the email correlation logic in Dynamics 365. Here are some steps to resolve the issue:
    1. Review Email Correlation Settings:
    • Dynamics 365 uses several methods to correlate emails with cases, including InReplyTo, Tracking Token, Conversation Index, and Smart Matching.
    • Verify which correlation method is active in your environment and adjust the settings as needed.
    2. Disable Smart Matching:
    • If Smart Matching is enabled, it may cause emails with similar subjects to be routed into existing cases. Consider disabling this feature if it’s not required.
    3. Modify Subject Line Requirements:
    • Ensure that customers use unique subject lines for new emails. This can help prevent unintended correlations.
    4. Use Custom Workflows or Power Automate:
    • Create a custom workflow or Power Automate flow to handle incoming emails. This allows you to define specific rules for case creation based on email content or metadata.
    5. Test and Validate:
    • After making changes, test the email routing process to ensure new emails are correctly creating cases.
     
    Hope this helps some!

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Microsoft Dynamics 365 | Integration, Dataverse, and general topics

#1
iampranjal Profile Picture

iampranjal 41

#2
Martin Dráb Profile Picture

Martin Dráb 38 Most Valuable Professional

#3
Satyam Prakash Profile Picture

Satyam Prakash 35

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans