cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Anonymous
Not applicable

Output property not updated after calling getOutputs undefined (React control)

I am creating a custom code control using the react framework. It is a text input that should return a text as output after the user entered text in the control.

Now I have the following manifest (shorted):

 

 

 

<?xml version="1.0" encoding="utf-8"?>
<manifest>
        <property name="Text"
                  display-name-key="Text"
                  description-key="Text of the text input"
                  of-type="SingleLine.Text"
                  usage="output"
                  required="true" />
        <resources>
...
        </resources>
    </control>
</manifest>

 

 

Then I have the following  index.ts:

 

 

imports ...
export class CustomTextInput implements ComponentFramework.ReactControl<IInputs, IOutputs> {
    private notifyOutputChanged: () => void;
    private _text: string | undefined;
    private _props: ITextInputProps;
    constructor() { }

  public init(
        context: ComponentFramework.Context<IInputs>,
        notifyOutputChanged: () => void,
     void {
        this.notifyOutputChanged = notifyOutputChanged;

        this._props = {
            // ... some properties
            default: context.parameters.Default.raw!,
            maxLength: context.parameters.MaxLength.raw!,
            onTextChange: this.onTextChange,
        }
        console.log("init calls this.onTextChange: " + JSON.stringify(this._props.default))
        this.onTextChange(this._props.default);
    }

 public updateView(context: ComponentFramework.Context<IInputs>): React.ReactElement {
        console.log("update view");
        if (context.updatedProperties.indexOf('Default') > -1 || this._props.default !== context.parameters.Default.raw!) {
            this._props.default = context.parameters.Default.raw!;
        }

        if (context.updatedProperties.indexOf('MaxLength') > -1 || this._props.maxLength !== context.parameters.MaxLength.raw!) {
            const newMaxLength = this._props.maxLength = context.parameters.MaxLength.raw!;
            if (this._text && this._text.length > newMaxLength) {
                this._text = this._text.substring(0, newMaxLength) || "";
            }
        }
        return React.createElement(
            TextInput, this._props
        );
    }

    public getOutputs(): IOutputs {
        console.log("getOutputs, this._text: " + JSON.stringify(this._text));
        return { Text: this._text } as IOutputs;
    }

    onTextChange = (newValue: string | undefined): void => {
        console.log("onTextChange");
        console.log("newValue: " + JSON.stringify(newValue));

        if (newValue && newValue.trim().length !== 0) {
            this._text = newValue;
        } else {
            this._text = undefined;
        }
        console.log(this._text);
        this.notifyOutputChanged();
    };

 

 

My React Component file TextInput.tsx looks like this:

 

 

imports ...
export interface ITextInputProps {
  default?: string;
  maxLength?: number;
  onTextChange: (newText: string) => void
}
export interface ITextInputState {
  text: string;
}

export class TextInput extends React.Component<ITextInputProps, ITextInputState> {
  constructor(props: ITextInputProps) {
    super(props);
    this.state = {
      text: props.default || ""
    };
  }

  public render(): React.ReactNode {
    return (
      <ThemeProvider theme={this.props.theme}>
        <TextInputContainer>
          <LabelsContainer>
            <Label>{this.props.label}</Label>
            {this.props.hasClearButton && <ClearLabel onClick={this.handleOnClear}>Clear</ClearLabel>}
          </LabelsContainer>
          <Input placeholder={this.props.hintText} value={this.state.text.trim() !== "" ? this.state.text : ""} spellCheck={this.props.shouldSpellCheck}
            onChange={this.handleInputChange} type={this.props.format === "Text" ? "text" : "number"}
            maxLength={this.props.maxLength} />
        </TextInputContainer>
      </ThemeProvider>
    )
  }

  componentDidUpdate(prevProps: ITextInputProps) {
    if (prevProps.maxLength !== this.props.maxLength || this.props.maxLength && this.props.maxLength < this.state.text.length) {
      const { maxLength, onTextChange } = this.props;
      let { text } = this.state;
      if (maxLength === undefined || maxLength === null) {
        text = "";
      } else if (maxLength && text.length > maxLength) {
        text = text.substring(0, maxLength);
      }
      this.setState({ text }, () => onTextChange(text));
    }
  }

  handleInputChange = (event: React.ChangeEvent<HTMLInputElement>) => {
    const newValue = event.target.value;
    console.log("handleInputChange: newValue: " + JSON.stringify(newValue));

    this.setState({
      text: newValue
    });

    this.props.onTextChange(newValue);
  }

  handleOnClear = () => {
    console.log("handleOnClear")
    console.log("this.state before: "+ JSON.stringify(this.state));

    this.setState({
      text: ""
    }, () => console.log("this.state after: " + JSON.stringify(this.state)));

    this.props.onTextChange("");
  }
}

 

 

 

When I add the code control to an app and I add a normal powerapps textlabel it looks like this:

Britninja_0-1681317808768.png

With TextLabel.Text being: "CustomTextInput1.Text: " & CustomTextInput1.Text

 

Now when I type text in the control it updates the label as well. Only if I try to delete all characters, it will stick with the old value unless I save and refresh the page.
Same thing when I hit the clear button: It deletes the content in the control, but doesn't update the value of CustomTextInput1.Text in the TextLabel. It looks like this (note the logs on the right).

Britninja_1-1681318176844.png

 

 

Does anyone know why it would not update the TextProperty although getOutputs is called with the undefined value?

 

Also note that in the test harness the output value also shows the value of undefined after activating the clear or deleting the letters. And if I delete the letters one by one in the power app it updates the label each time except for the last letter (control input is empty but CustomTextInput1.Text shows the last letter).

3 REPLIES 3
DianaBirkelbach
Most Valuable Professional
Most Valuable Professional

Hi @Anonymous , 

 

It's a little hard to follow... not sure if I get it right, since I don't really understand what the PCF should do.
But usually for this kind of issues it's important to understand how the updateView works.

When a value changes inside the PCF, and you call the notifyOutputChanges(), the getOutputs gets called by the platform. Then the Platform Runtime evaluates the value, and then calls the updateView again, providing the new value. So after that the updateView will be called, and your TextInput component will rerender. 

I guess the problems are cased by the TextInput component using an internal state for the "text", which doesn't get updated after the updateView. 

Have a look to this PCF-Tutorial from the docs, and the explanation about "Controlled React component": https://learn.microsoft.com/en-us/power-apps/developer/component-framework/tutorial-create-model-driven-field-component?tabs=before&WT.mc_id=BA-MVP-5004107#controlled-react-component

 

Hope it helps!

Kind regards,
Diana
----------
Please click "Accept as Solution" if my post answered your question so that others may find it more quickly. If you found this post helpful consider giving it a "Thumbs Up."

Hello @DianaBirkelbach ! Thank you for replying!

 

Sorry if my question was confusing.

What does the control do?

The control is a custom text input. The app user clicks in it, types something and can provide that way a string input (not via a property in the property panel, but by using the control).

That input value should be reusable in the app. So I need to get its value as output from the control.

The property I am using for this is called "Text".

So CustomTextInput1.Text should return the value that was provided by the user in the control.


What does work?

Now when I type for example "Apple" and I delete letters one by one (or a chunk of them) the output value (CustomTextInput1.Text) is visibly updated. So Text is updated on text changes (when they are not empty string).

What is the problem?
BUT, when I remove all letters,(or use the "onClear" function) that is, when the control input is completely empty (empty string), it does NOT update the value in CustomTextInput1.Text to be Blank().

I am using state.text for containing and displaying the user input and it does work as expected (state.text is "" when deleting all the letters, also the control shows that it is empty). BUT the output value of the property seems to not be taken correctly when it's an empty string (undefined) value.

The thing is, I do call the props.onTextChange() with the value of "" (empty string). it propagates through to the getOutputs method and actually does return "undefined" as output value (as the logs show). But still the CustomTextInput1.Text variable does not show the updated value.

TDLR;
getOutputs returns {Text: undefined} but the corresponding output variable CustomTextInput1.Text in the App still contains the last value that is not undefined unless I save and refresh the page.

Hope this  helps to get a better understanding. I have the feeling state.text is not the problem, because getOutputs does return undefined. 

Also notice that in the logs updateView is called, it shows state.text before the update and state.text after the update and its value shows empty string.

Britninja_0-1681488429101.png

Anonymous
Not applicable

I was able to solve my problem by returning null instead of undefined in handleInputChange. I think this causes the output property to be read as or converted to "Blank()" in Power Apps.

So my code now looks like this:
index.ts

    onTextChange = (newValue: string | undefined): void => {
       // ...

        if (newValue && newValue.trim().length !== 0) {
            this._text = newValue;
        } else {
            this._text = null;
        }
        // ...
        this.notifyOutputChanged();
    };

 TextInput.tsx (didn't really change anything except I am using the handleInputChange method now)

      <ClearLabel onClick={() => isEditMode ? this.handleInputChange("") : {}}
      className={displayMode?.toLowerCase()}>Clear</ClearLabel>

 
Interestingly enough it seems I get the following errors in the testharness (but the code runs as it should).

Britninja_0-1682100813124.png

 

But in my app I don't get these errors so maybe that's something about updating values in the test harness.

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

Users online (570)