cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Rubened
Frequent Visitor

PCF Fluent UI Action button context.mode.trackContainerResize not updating width.

Hi,

 

I am new to PCF, React and Fluent UI, but I started playing with some components form the PCF Gallery, mainly the Action button made by MscrmTools.

My goal was to make the button width responsive to the available space in the container the button is located in.

I have found the following function which is supposed to make this possible: 

This function allows the button to read the dimensions of the container through context.mode.allocatedWidth and context.mode.allocatedHeight and also kicks off the UpdateView if any of the container dimensions change.

 

This function does indeed kick of the UpdateView but for some reason the width of the button does not change. For example when I change the zoom of the page in a model-driven app it does put the correct pixel value into the width prop of the component but does not update the button accordingly.

 

I have added the following parts to the code of MscrmTools:

  • index.ts

 

 

import { IInputs, IOutputs } from "./generated/ManifestTypes";
import * as React from 'react';
import * as ReactDOM from 'react-dom';
import ButtonControl, { IButtonControlProps } from "./QssFancyButton";
import { initializeIcons } from '@fluentui/font-icons-mdl2';


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

	private container: HTMLDivElement;
	private notifyOutputChanged: () => void;
	private currentValue: string | null;
	private buttonLabel: string;
	private id: string;
	private sendId: boolean;
	private controlType: string;
	/**
	 * Empty constructor.
	 */
	constructor() 
	{
		initializeIcons();
	}

	/**
	 * 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) 
   {
		this.container = container;
		this.notifyOutputChanged = notifyOutputChanged;

		this.buttonLabel = context.parameters.buttonLabel.raw ?? "";
		this.id = context.parameters.buttonId.raw ?? "";
		this.sendId = context.parameters.sendId.raw === "1";
		context.mode.trackContainerResize(context.parameters.trackContainerResizeValue.raw === "1" ? true : false);

		// @TS-ignore
		this.controlType = context.parameters.buttonAttribute.attributes.Type;

		if (this.buttonLabel.trim().startsWith("{")) 
      {
			let json = JSON.parse(this.buttonLabel);
			try 
         {
				this.buttonLabel = json[context.userSettings.languageId];
				if (this.buttonLabel === undefined) 
            {
					this.buttonLabel = json[parseInt(Object.keys(json)[0])];
				}
			}
			catch 
         {
				this.buttonLabel = json[parseInt(Object.keys(json)[0])];
			}
		}

		this.renderControl(context);
	}

	private renderControl(context: ComponentFramework.Context<IInputs>): void 
   {

		let props: IButtonControlProps = 
      {
			text: this.buttonLabel,
			disabled: context.parameters.enableButtonOnDisabledForm.raw === "1" ? false : context.mode.isControlDisabled,
			style: 
         {
				backgroundColor: context.parameters.backgroundColor.raw ?? "#0078d4",
				borderColor: context.parameters.borderColor.raw ?? "#0078d4",
				color: context.parameters.textColor.raw ?? "#FFFFFF",
				width: context.parameters.trackContainerResizeValue.raw === "1" ? `${context.mode.allocatedWidth}px` : context.parameters.trackContainerResizeValue.raw === "0" && context.parameters.width.raw !== null ? context.parameters.width.raw : "auto"
			},
			hoverBackgroundColor: context.parameters.hoverBackgroundColor.raw ?? "#106EBE",
			hoverBorderColor: context.parameters.hoverBorderColor.raw ?? "#106EBE",
			hoverColor: context.parameters.hoverTextColor.raw ?? "#FFFFFF",
			checkedBackgroundColor: context.parameters.pressedBackgroundColor.raw ?? "#0078d4",
			checkedBorderColor: context.parameters.pressedBorderColor.raw ?? "#0078d4",
			checkedColor: context.parameters.pressedTextColor.raw ?? "#FFFFFF",
			iconName: context.parameters.iconName.raw,
			toolTip: context.parameters.tooltipText.raw ?? "",
			onClick: () => { this.notifyOutputChanged(); }
		}

		ReactDOM.render(React.createElement(ButtonControl, props), this.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 
	{
		this.renderControl(context);

		this.currentValue = context.parameters.buttonAttribute.raw ?? "";
	}

	/** 
	 * 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 
	{
		if (this.controlType === "string") 
		{
			return {
				buttonAttribute: this.sendId ? this.id : this.buttonLabel
			};
		}

		return {
			buttonAttribute: new Date()
		};
	}

	/** 
	 * 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
	}
}

 

 

  • Inside the public init:

    • context.mode.trackContainerResize(context.parameters.trackContainerResizeValue.raw === "1" ? true : false);

  • Inside the private renderControl:

    • width: context.parameters.trackContainerResizeValue.raw === "1" ? `${context.mode.allocatedWidth}px` : context.parameters.trackContainerResizeValue.raw === "0" && context.parameters.width.raw !== null ? context.parameters.width.raw : "auto"

  • ControlManifest.Input.xml

    • <property name="trackContainerResizeValue" display-name-key="trackContainerResizeValue_Display_Key" description-key="trackContainerResizeValue_Desc_Key" of-type="Enum" default-value="0" usage="input" required="true"> <value name="true" display-name-key="yes_Resize_Display_Key" description-key="yes_Resize_Desc_Key">1</value> <value name="false" display-name-key="no_Resize_Display_Key" description-key="no_Resize_Desc_Key">0</value> </property>

I did not change anything in the .tsx as there was no need to, if I'm not mistaken.
The following happens when changing the width of the component container in npm start watch, or from a model-driven app:

  • Run through index.ts
  1. trackContainerResizeValue = true
     
    Rubened_4-1719311226714.png
     
  2. width: 600px, sometimes it reads -1px but after a second run of renderControl(context) it does return a valid pixel value (only in npm start watch).
     
    Rubened_5-1719311238091.png
  3. Width of button does not change:
     
    Rubened_6-1719311248820.png

If anybody is willing to help me out that would be great, if you need my files, let me know but they are basically the same as MscrmTools his code with the lines above added to it.

1 ACCEPTED SOLUTION

Accepted Solutions
Rubened
Frequent Visitor

A coworker of mine has found the solution.
Ignoring context.mode.trackContainerResize and instead utilizing width 100% he managed to fix the issue.
Apparently, in this component if you don't set the width of the tooltip with the width of the button this behavior happens.

So my coworker fixed it with the following added:

  1. import { TooltipHostITooltipHostStyles from '@fluentui/react/lib/Tooltip';
  2.    tooltipStylesITooltipHostStyles = {
           root: {
               width: this.props.style?.width
           }
       }
  3. return (
               <Stack horizontal>
                   {this.props.text?.trim().length ? (
                       <TooltipHost content={this.props.toolTip} id={toolTipId} styles={this.tooltipStyles}>
                           <PrimaryButton
                               iconProps={this.icon}
                               styles={this.styles}
                               text={this.props.text}
                               disabled={this.props.disabled}
                               onClick={this.props.onClick}
                               aria-describedby={toolTipId}
                           />
                       </TooltipHost>
                   ) 

The code now works as intended and looks as follows:

 

import * as React from 'react'
import { Stack } from '@fluentui/react/lib/Stack';
import { IBaseButtonProps, IBaseButtonState, IButtonStyles, PrimaryButton, IconButton } from '@fluentui/react/lib/Button';
import { IIconProps } from '@fluentui/react';
import { TooltipHost, ITooltipHostStyles } from '@fluentui/react/lib/Tooltip';

export interface IButtonControlProps extends IBaseButtonProps {
    hoverBackgroundColor: string,
    hoverBorderColor: string,
    hoverColor: string,
    checkedBackgroundColor: string,
    checkedBorderColor: string,
    checkedColor: string,
    iconName: string | null,
    toolTip: string | undefined,
}

export default class ButtonControl extends React.Component<IButtonControlProps, IBaseButtonState>{
    constructor(props: IButtonControlProps) {
        super(props);
    }
    styles: IButtonStyles = {
        root: {
            backgroundColor: this.props.style?.backgroundColor ?? "#0078d4",
            borderColor: this.props.style?.borderColor ?? "#0078d4",
            color: this.props.style?.color ?? "#FFFFFF",
            width: this.props.style?.width
        },
        rootHovered: {
            backgroundColor: this.props.hoverBackgroundColor ?? "#106EBE",
            borderColor: this.props.hoverBorderColor ?? "#106EBE",
            color: this.props.hoverColor ?? "#FFFFFF",
            width: this.props.style?.width
        },
        rootPressed: {
            backgroundColor: this.props.checkedBackgroundColor ?? "#0078d4",
            borderColor: this.props.checkedBorderColor ?? "#0078d4",
            color: this.props.checkedColor ?? "#FFFFFF",
            width: this.props.style?.width
        }
    }
    tooltipStyles: ITooltipHostStyles = {
        root: {
            width: this.props.style?.width
        }
    }

    icon: IIconProps = { iconName: this.props.iconName ?? "" };

    render() {
        const toolTipId = `tooltip_${this.props.iconName}`;

        return (
            <Stack horizontal>
                {this.props.text?.trim().length ? (
                    <TooltipHost content={this.props.toolTip} id={toolTipId} styles={this.tooltipStyles}>
                        <PrimaryButton
                            iconProps={this.icon}
                            styles={this.styles}
                            text={this.props.text}
                            disabled={this.props.disabled}
                            onClick={this.props.onClick}
                            aria-describedby={toolTipId}
                        />
                    </TooltipHost>
                ) : (
                    <TooltipHost content={this.props.toolTip} id={toolTipId} styles={this.tooltipStyles}>
                        <IconButton
                            iconProps={this.icon}
                            styles={this.styles}
                            disabled={this.props.disabled}
                            onClick={this.props.onClick}
                            aria-describedby={toolTipId}
                        />
                    </TooltipHost>
                )}
            </Stack>
        );
    }
}

 

 

View solution in original post

3 REPLIES 3
a33ik
Most Valuable Professional
Most Valuable Professional

Hello,

Did you try to set the button width to "100%"?

Hi a33ik,

 

Thank you for your response.

Unfortunately, when I put 100% into the width variable it just looks at the PCF container itself which is as big as the label and icon with some margin, it does not look, natively, at the container in a Model-driven app it is located.

 

I build in the possibility to put a width manually which you can see in the following screenshot:

Rubened_0-1719494218389.png

But it does not change the width of the button to fit the whole section as you can see in the left part of the screenshot.

To translate the options for the control:

  • Volg Container Breedte = The option to set whether context.mode.trackContainerResize is true (Ja) or not (Nee).
    • If this option is true (Ja), it will ignore the value that the user put in Width (Breedte).
  • Breedte = Width of the button.

Once I put in a value like 250% or 500px into the width property manually it does make the button bigger:

Rubened_1-1719494588092.png

But when context.mode.trackContainerResize dynamically, for example when the size of the page changes, puts in a pixel value through context.mode.allocatedWidth into the width property of the button it does not change. which is strange.

Rubened
Frequent Visitor

A coworker of mine has found the solution.
Ignoring context.mode.trackContainerResize and instead utilizing width 100% he managed to fix the issue.
Apparently, in this component if you don't set the width of the tooltip with the width of the button this behavior happens.

So my coworker fixed it with the following added:

  1. import { TooltipHostITooltipHostStyles from '@fluentui/react/lib/Tooltip';
  2.    tooltipStylesITooltipHostStyles = {
           root: {
               width: this.props.style?.width
           }
       }
  3. return (
               <Stack horizontal>
                   {this.props.text?.trim().length ? (
                       <TooltipHost content={this.props.toolTip} id={toolTipId} styles={this.tooltipStyles}>
                           <PrimaryButton
                               iconProps={this.icon}
                               styles={this.styles}
                               text={this.props.text}
                               disabled={this.props.disabled}
                               onClick={this.props.onClick}
                               aria-describedby={toolTipId}
                           />
                       </TooltipHost>
                   ) 

The code now works as intended and looks as follows:

 

import * as React from 'react'
import { Stack } from '@fluentui/react/lib/Stack';
import { IBaseButtonProps, IBaseButtonState, IButtonStyles, PrimaryButton, IconButton } from '@fluentui/react/lib/Button';
import { IIconProps } from '@fluentui/react';
import { TooltipHost, ITooltipHostStyles } from '@fluentui/react/lib/Tooltip';

export interface IButtonControlProps extends IBaseButtonProps {
    hoverBackgroundColor: string,
    hoverBorderColor: string,
    hoverColor: string,
    checkedBackgroundColor: string,
    checkedBorderColor: string,
    checkedColor: string,
    iconName: string | null,
    toolTip: string | undefined,
}

export default class ButtonControl extends React.Component<IButtonControlProps, IBaseButtonState>{
    constructor(props: IButtonControlProps) {
        super(props);
    }
    styles: IButtonStyles = {
        root: {
            backgroundColor: this.props.style?.backgroundColor ?? "#0078d4",
            borderColor: this.props.style?.borderColor ?? "#0078d4",
            color: this.props.style?.color ?? "#FFFFFF",
            width: this.props.style?.width
        },
        rootHovered: {
            backgroundColor: this.props.hoverBackgroundColor ?? "#106EBE",
            borderColor: this.props.hoverBorderColor ?? "#106EBE",
            color: this.props.hoverColor ?? "#FFFFFF",
            width: this.props.style?.width
        },
        rootPressed: {
            backgroundColor: this.props.checkedBackgroundColor ?? "#0078d4",
            borderColor: this.props.checkedBorderColor ?? "#0078d4",
            color: this.props.checkedColor ?? "#FFFFFF",
            width: this.props.style?.width
        }
    }
    tooltipStyles: ITooltipHostStyles = {
        root: {
            width: this.props.style?.width
        }
    }

    icon: IIconProps = { iconName: this.props.iconName ?? "" };

    render() {
        const toolTipId = `tooltip_${this.props.iconName}`;

        return (
            <Stack horizontal>
                {this.props.text?.trim().length ? (
                    <TooltipHost content={this.props.toolTip} id={toolTipId} styles={this.tooltipStyles}>
                        <PrimaryButton
                            iconProps={this.icon}
                            styles={this.styles}
                            text={this.props.text}
                            disabled={this.props.disabled}
                            onClick={this.props.onClick}
                            aria-describedby={toolTipId}
                        />
                    </TooltipHost>
                ) : (
                    <TooltipHost content={this.props.toolTip} id={toolTipId} styles={this.tooltipStyles}>
                        <IconButton
                            iconProps={this.icon}
                            styles={this.styles}
                            disabled={this.props.disabled}
                            onClick={this.props.onClick}
                            aria-describedby={toolTipId}
                        />
                    </TooltipHost>
                )}
            </Stack>
        );
    }
}

 

 

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

We are excited to announce the Summer of Solutions Challenge!   This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions in the Forums to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersNumber of SolutionsSuper UsersNumber of Solutions @anandm08  23 @WarrenBelz  31 @DBO_DV  10 @Amik  19 AmínAA 6 @mmbr1606  12 @rzuber  4 @happyume  7 @Giraldoj  3@ANB 6 (tie)   @SpongYe  6 (tie)     Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersSolutionsSuper UsersSolutions @anandm08  10@WarrenBelz 25 @DBO_DV  6@mmbr1606 14 @AmínAA 4 @Amik  12 @royg  3 @ANB  10 @AllanDeCastro  2 @SunilPashikanti  5 @Michaelfp  2 @FLMike  5 @eduardo_izzo  2   Meekou 2   @rzuber  2   @Velegandla  2     @PowerPlatform-P  2   @Micaiah  2     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 3:Community MembersSolutionsSuper UsersSolutionsPower Apps anandm0861WarrenBelz86DBO_DV25Amik66Michaelfp13mmbr160647Giraldoj13FLMike31AmínAA13SpongYe27     Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 4:Community MembersSolutionsSuper UsersSolutionsPower Apps DBO-DV21WarranBelz26Giraldoj7mmbr160618Muzammmil_0695067Amik14samfawzi_acml6FLMike12tzuber6ANB8   SunilPashikanti8

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages