I've created my own Lookup PCF for my model driven app; it's quite a complicated control that gives the user a load of different options for populating the control, and the control works perfectly for setting a value however I cannot find a way to clear the value once it has been set (the equivalent of clicking the X next to the value in a normal OOB lookup control).
Looking at the sample PCF for a lookup (LookupSimpleControl), it passes in a function to set the value of the local property, which is then returned by the getOutputs(), using the value {} as ComponentFramework.LookupValue, as detailed below:
Global Variables used in the sample control:
// Used to store necessary data for a single lookup entity selected during runtime
private _selectedItem1: ComponentFramework.LookupValue;
private _selectedItem2: ComponentFramework.LookupValue;
// Used to track which lookup property is being updated
private _updateSelected1 = false;
Where the event is bound and the variable value is set
lookupObjectsButton1.onclick = this.performLookupObjects.bind(this, this._entityType1, this._defaultViewId1, (value, update = true) => {
this._selectedItem1 = value;
this._updateSelected1 = update;
});
The method setting (and clearing) the value:
private performLookupObjects(entityType: string, viewId: string, setSelected: (value: ComponentFramework.LookupValue, update?: boolean) => void): void {
// Used cached values from lookup parameter to set options for lookupObjects API
const lookupOptions = {
defaultEntityType: entityType,
defaultViewId: viewId,
allowMultiSelect: false,
entityTypes: [entityType],
viewIds: [viewId]
};
this._context.utils.lookupObjects(lookupOptions).then((success) => {
if (success && success.length > 0) {
// Cache the necessary information for the newly selected entity lookup
const selectedReference = success[0];
const selectedLookupValue: ComponentFramework.LookupValue = {
id: selectedReference.id,
name: selectedReference.name,
entityType: selectedReference.entityType
};
// Update the primary or secondary lookup property
setSelected(selectedLookupValue);
// Trigger a control update
this._notifyOutputChanged();
} else {
setSelected({} as ComponentFramework.LookupValue);
}
}, (error) => {
console.log(error);
});
}
getOutputs method:
public getOutputs(): IOutputs {
// Send the updated selected lookup item back to the ComponentFramework, based on the currently selected item
return this._updateSelected1 ? { controlValue: [this._selectedItem1] } : { controlValue1: [this._selectedItem2] };
}
How the properties are registered in the ControlManifest.Input.xml file:
<property name="controlValue" display-name-key="controlValue_Display_Key" description-key="controlValue_Desc_Key" of-type="Lookup.Simple" usage="bound" required="true" />
<property name="controlValue1" display-name-key="controlValue_Display_Key1" description-key="controlValue_Desc_Key1" of-type="Lookup.Simple" usage="bound" required="true" />
This is essentially the same way my control works, except I'm not using the lookupObjects method, and have a button to clear the value.
My global variable:
private _selectedItem: ComponentFramework.LookupValue;
My event binding:
this._buttonClearField.onclick = this.onClearClick.bind(this, (value) => {
this._selectedItem = value;
});
My click event which clears the value:
private async onClearClick(setSelected: (value: ComponentFramework.LookupValue) => void) {
// Clear the lookup property
setSelected({} as ComponentFramework.LookupValue);
}
My getOutputs method:
public getOutputs(): IOutputs
{
return { boundField: [this._selectedItem] };
}
My control property:
<property name="boundField" display-name-key="Bound Field" description-key="The field the control is bound to" of-type="Lookup.Simple" usage="bound" required="true" />
This looks the same to me. After the clear event runs, the _selectedItem property is cleared, but the context.parameters.boundField value doesn't seem to get updated, and when the record on the form is saved, the field value isn't cleared. I've tried calling notifyOutputChanged, manually clearing the value from context.parameters.boundField, but the field value just doesn't get cleared.
I haven't managed to get the sample PCF working yet to see if that actually works, that's my next step (I'm just setting up and env and app I can use for that.
Is there anything in the above that looks wrong? Has anyone else encountered this issue, or managed to clear a bound lookup value from their PCF? Please help, this has been driving me nuts for a few weeks now.
Solved! Go to Solution.
Hi @Polmon ,
You're right, you need to set the value to undefined.
Of course you need to change the onClearClick, to set the value to undefined (not to {}).
The notifyOutputChanged need to be called too.
Can you please check with the debugger or logging that the value passed through getOutputs is undefined...
Yes, I've just checked, and I can clear the value of a lookup that way.
I've changed the first answer with this details, just to have them all together.
Hope this helps!
I've had a chance to try out the sample control now, and the cancel function (where it uses the setSelected function to return {} as ComponentFramework.LookupValue) doesn't do anything unfortunately, it just cancels the lookup dialog without returning a value to update the bound property. Still no idea how to clear the bound property of a lookup PCF unfortunately.
Hi @Polmon ,
try to change the getOutputs to something like this
public getOutputs(): IOutputs
{
return { boundField: this._selectedItem ? [this._selectedItem] : undefined };
}
Using the "return {}" will not change any property, you need to pass undefined in order to notify the framework that your value was changed/removed.
Of course you need to change the onClearClick to set the value on undefined
private async onClearClick(setSelected: (value: ComponentFramework.LookupValue) => void) {
// Clear the lookup property
setSelected(undefined);
}
Inside the "setSelected" you need to call the
this._notifyOutputChanged()
Hope this helps!
Hi Diana, I've just had a go at that; I can't use null as boundField is ComponentFramework.LookupValue[] | undefined, so I tried using undefined instead as follows:
public getOutputs(): IOutputs
{
return { boundField: this._selectedItem ? [this._selectedItem] : undefined};
}
Unfortunately, this didn't work, clearing the field doesn't show the form as unsaved and saving subsequently doesn't clear the field. I also tried using {} as ComponentFramework.LookupValue in getOutputs too as shown below, but that doesn't work either.
public getOutputs(): IOutputs
{
return { boundField: this._selectedItem ? [this._selectedItem] : {} as ComponentFramework.LookupValue};
}
I tried dropping notifyOutputChanged in to my clear button event too, but that didn't make a difference either.
Have you managed to get this working?
Hi @Polmon ,
You're right, you need to set the value to undefined.
Of course you need to change the onClearClick, to set the value to undefined (not to {}).
The notifyOutputChanged need to be called too.
Can you please check with the debugger or logging that the value passed through getOutputs is undefined...
Yes, I've just checked, and I can clear the value of a lookup that way.
I've changed the first answer with this details, just to have them all together.
Hope this helps!
Yes! That was it. I needed to change the declaration of the value everywhere it was used, but it's working now.
For the benefit of anyone else, I'll detail below the working setup.
The variable that's returned:
private _selectedItem: ComponentFramework.LookupValue | undefined;
The binding for the button click event (the _notifyOutputChanged reference is set to the parameter passed into the init function):
this._buttonClearField.onclick = this.onClearClick.bind(this, (value) => {
this._selectedItem = value;
this._notifyOutputChanged();
});
The clear button click implementation:
private async onClearClick(setSelected: (value: ComponentFramework.LookupValue | undefined) => void) {
// Clear the lookup property
setSelected(undefined);
}
In getOutputs, just pass back the value or undefined (I could probably just pass back _selectedItem here without the check):
public getOutputs(): IOutputs
{
return { boundField: this._selectedItem ? [this._selectedItem] : undefined };
}
And that's it, the value is cleared on click now. Thank you @DianaBirkelbach!
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!
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
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.
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