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

Resetting a code component bound property

Hello, I created a custom control which is imported in a canvas app. The control has a bound property whose value is processed whenever UpdateView is called. I want to process the incoming value only when a PowerApps variable bound to the control property is updated(when I'm getting new user input). 

 

The issue is that UpdateView gets called multiple times between user inputs(between variable updates). This means I'm reading repeated, outdated values for the parameter.

 

User Input

Control property 

Action in UpdateView

"First input"

"First input"

Process this

no input

"First input"

Need to ignore this

no input

"First input"

Need to ignore this

"Second Input"

"Second input"

Process this

no input

"Second input"

Need to ignore this

My intent is to set the control property to empty string after processing user input, and ignore input values equal to empty strings. Comparing the current value with the previous one is not an option, since the user might provide the same value twice.

 

Is there a way to achieve this, either inside the control or with PowerApps code?

1 ACCEPTED SOLUTION

Accepted Solutions
DianaBirkelbach
Most Valuable Professional
Most Valuable Professional

Hi @Anonymous , 

 

I think I've got your use-case now: you want to use the PCF only for processing the text using a 3rd party library.

You won't have control over when updateView is called, so we will have to find a way to take the control.

 

Also triggering notifyOutputChanged in updateView could lead to a loop of async calls, since every time you change the value the updateView will be called again (kind of self-triggering).

 

Solution idea 0

A clasical solution to this would be implementing both the input and the button inside your PCF. Then you would notify tha platform only for the values you've processed with 3rd party library.

 

But I guess that's not what you are looking for, since it's easier to use the CanvasApp controls. So I would propose this PCF design

Solution idea 

Define 3 properties for your PCF: an input for the input text, a trigger property and an output property.

  1. inputValue property, the same as you did. Maybe the variable is not needed, if you set the property directly
    1. youtPCF.inputValue = inputValueBox.text
  2. triggerProperty. This one will be set each time the user clicks on the button. This way it doesn't matter that the value in the text box is not changed. In updateView you process the inputValue only when the value of the triggerProperty changes.
    1. As trigger property you could use a timestamp (datetime). This way you don't need to reset
    2. Anothe approach is to use an integer, which you increment each time the button is clicked
    3. You don't need to reset, but if you want to, you can reset the value of the triggerProperty from inside the PCF (using a small delay (window.setTimeout)). But then you need to ignore the null/reseted values inside updateView
  3. outputProperty: This property is of type "output" and here you can put the processed values using the 3rs Party library (and of course call notifyOutputChanged). Since it's separate from the inputProperty, you won't have issues with self-triggering.
  1.  

Hope this 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."

View solution in original post

4 REPLIES 4
DianaBirkelbach
Most Valuable Professional
Most Valuable Professional

Hi @Anonymous , 

Having the updateView called multiple times is by design.
I'm not so sure if I understand your use case  (seems a little tricky), but inside the PCF updateView you can examine the context.updatedProperties. That way you will know what was changed last (what's the reason of calling the updateView).
In case you change the value of your properties inside your PCF too, be aware that this will trigger another updateView for your own PCF. Seems that you need to ignore the cases when the value is empty, since that's what you reseted lastly.


If this doesn't help, maybe you can explain a little more about your use case. Would be happy to brainstorm with you.

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."

Hi Diana,

It would be useful to know the reason UpdateView is called. If a property of interest has changed, I could process its value. I examined context.updatedProperties, however it did not contain any of the bound properties after updating values in the harness. The only thing that showed up was a property called "layout".

 

I'll try to provide more context on my use case.

 

I have a Canvas app containing my custom control, a variable ‘varInputValue’ bound to the control’s ‘inputValue’ property, a textbox ‘inputValueBox’ and a button with an action Set(varInputValue, inputValueBox.text).

 

Whenever the user clicks the button, the string in the textbox is passed as input to my custom control. I process the user input with a 3rd party library inside the control:

    

 

public updateView(context: ComponentFramework.Context<IInputs>): void {
    
    let inputValue = context.parameters.inputValue.raw; // the value of the parameter is persisted between UpdateViews. I do not want to process the same value every time UpdateView is called, unless a new input comes from the user(the new input can be the same string as the old input), obtained through a Set Action.
    
    if (!this.isNOUOE(inputValue) && inputValue !== 'val'){
        this._inputValue = inputValue;
        
        // Process inputValue with a 3rd party library    
        
        this._notifyOutputChanged();
    }
}

public getOutputs(): IOutputs {
    return {
        inputValue: this._inputValue
    };
}

 

If I could reset the 'inputValue' property to empty string after running UpdateView , I can be sure that input values that are not empty strings are new user inputs.

 

Maybe there is a way to do this using Power Apps code. I tried resetting the property in the same formula, using consecutive actions:

Set(varInputValue,"Testing this input");
Set(varInputValue,"");

The framework executes only the last action.

 

Thanks for your help.

 

DianaBirkelbach
Most Valuable Professional
Most Valuable Professional

Hi @Anonymous , 

 

I think I've got your use-case now: you want to use the PCF only for processing the text using a 3rd party library.

You won't have control over when updateView is called, so we will have to find a way to take the control.

 

Also triggering notifyOutputChanged in updateView could lead to a loop of async calls, since every time you change the value the updateView will be called again (kind of self-triggering).

 

Solution idea 0

A clasical solution to this would be implementing both the input and the button inside your PCF. Then you would notify tha platform only for the values you've processed with 3rd party library.

 

But I guess that's not what you are looking for, since it's easier to use the CanvasApp controls. So I would propose this PCF design

Solution idea 

Define 3 properties for your PCF: an input for the input text, a trigger property and an output property.

  1. inputValue property, the same as you did. Maybe the variable is not needed, if you set the property directly
    1. youtPCF.inputValue = inputValueBox.text
  2. triggerProperty. This one will be set each time the user clicks on the button. This way it doesn't matter that the value in the text box is not changed. In updateView you process the inputValue only when the value of the triggerProperty changes.
    1. As trigger property you could use a timestamp (datetime). This way you don't need to reset
    2. Anothe approach is to use an integer, which you increment each time the button is clicked
    3. You don't need to reset, but if you want to, you can reset the value of the triggerProperty from inside the PCF (using a small delay (window.setTimeout)). But then you need to ignore the null/reseted values inside updateView
  3. outputProperty: This property is of type "output" and here you can put the processed values using the 3rs Party library (and of course call notifyOutputChanged). Since it's separate from the inputProperty, you won't have issues with self-triggering.
  1.  

Hope this 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."
Anonymous
Not applicable

Hi Diana, 

Yes, this approach works. The triggerProperty allows me to determine if a new user input has been received. Thank you for your help.

 

Regards,

Dan

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 (1,355)