Hi,
I've developed a working PCF control that includes a save button with the event (saveResponsesHandler). I'm interested in leveraging the Dynamics 365 form's save button.
When I click the save button on the Dynamics 365 form,
I can see the PCF control's updateview function getting triggered. However, I'm unsure how to replace the save button within the PCF control with the one from the Dynamics 365 form.
Is there an example on how to accomplished this?
export const QuestionInputStack: React.FC<QuestionInputStackProps> = ({ questions, saveResponses, responses }) => {
const [loadedResponses, setLoadedResponses] = React.useState<{ [key: string]: any }>(responses);
const saveResponsesHandler = async () => {
const newResponses: any[] = [];
const isUpdate = Object.keys(loadedResponses).length > 0;
// Collect responses from inputs
questions.forEach((question: any, index: number) => {
const inputElement = document.getElementById(`questionInput_${index}`) as HTMLInputElement;
if (inputElement) {
let response: any = {
lfs_name: question.lfs_name,
lfs_inputresponse: inputElement.value
};
response["lfs_QuestionId@odata.bind"] = `/lfs_questions(${question.lfs_questionid})`;
//response["lfs_QuestionGroupId@odata.bind"] = `/lfs_questiongroups(${question.lfs_questiongroupid})`;
//response["ContactIdd@odata.bind"] = `/contact(${question.lfs_questionid})`;
// If it's an update, include lfs_questionresponseid if available
if (isUpdate) {
const existingResponse = loadedResponses[question.lfs_questionid];
if (existingResponse && existingResponse.lfs_contactquestionresponseid) {
response["lfs_contactquestionresponseid"] = existingResponse.lfs_contactquestionresponseid;
}
}
newResponses.push(response);
}
});
// Call saveResponses function from props
await saveResponses(newResponses, isUpdate);
setLoadedResponses(newResponses.reduce((acc, cur) => {
acc[cur.lfs_questionid] = cur;
return acc;
}, {}));
};
React.useEffect(() => {
console.log("Responses prop:", responses);
if (typeof responses === 'object' && responses !== null) {
const mappedResponses: { [questionId: string]: any } = {};
Object.keys(responses).forEach((key) => {
const cur = responses[key];
console.log("Current response:", cur);
mappedResponses[key] = cur;
});
console.log("Mapped responses:", mappedResponses);
setLoadedResponses(mappedResponses);
} else {
console.error("Responses is not an object or is null:", responses);
}
}, [responses]);
const handleChange = (value: string, questionId: string) => {
setLoadedResponses(prevState => ({
...prevState,
[questionId]: {
...prevState[questionId],
lfs_inputresponse: value
}
}));
};
return (
<Stack>
{questions.map((question: any, index: number) => {
const questionResponse = loadedResponses[question.lfs_questionid] || {}; // Get the response for the current question
return (
<div key={index} className="input-container">
<Label className="label">{question.lfs_translationname}</Label>
<QuestionInput
id={`questionInput_${index}`}
dataTypeName={question["lfs_questiondatatype@OData.Community.Display.V1.FormattedValue"]}
isRequired={question.lfs_isinputrequired}
decimalNumberFormat={question.lfs_decimalnumberformat}
minNumber={question.lfs_min}
maxNumber={question.lfs_max}
pattern={question.lfs_pattern}
value={questionResponse.lfs_inputresponse || ''}
onChange={(value: string) => handleChange(value, question.lfs_questionid)}
/>
</div>
);
})}
<button onClick={saveResponsesHandler}>Save</button>
</Stack>
);
};
Solved! Go to Solution.
There's no way to achieve this beside what I've mentioned:
PCFs are bound to either a dataset or a field. This means they don't have access to the form context and so can't trigger a save of all the form values, but can be part of the form. Check out the documentation for what a PCF component can do here: https://learn.microsoft.com/en-us/power-apps/developer/component-framework/reference/
For datasets (i.e. subgrids) you have options like setvalue and save - but these only work for the records in the dataset.
For fields you have getoutputs (see second link as the MS documentation around this isn't great)
You can also update through the webapi
So your options would be to have it bound to a field that triggers a save via the client api (https://learn.microsoft.com/en-us/power-apps/developer/model-driven-apps/clientapi/reference) or have the form update via a webapi update. Personally, if this is for a model-driven app I wouldn't do either of those and instead just get your users to use the ribbon save button after you've set the values to the bound fields.
I wanted to share some updates regarding the PCF control I've been working on. This control serves as a dynamic tool for users to input multiple questions seamlessly. To integrate it into our system, I created a field named "pcfField" and embedded the PCF control within it, utilizing a custom PCF control template designed specifically for fields.
Now, while the PCF control includes its own button, my aim is to streamline the process by utilizing the ribbon save button on the form. Upon clicking this button, I intend for it to seamlessly trigger the save function within the PCF control.
Your insights and guidance on achieving this integration efficiently would be greatly appreciated.
There's no way to achieve this beside what I've mentioned:
Thanks for the help.
One more question.
Is there a way to trigger the function I have in the pcf control that will update the dataverse using the webAPI.createrecord or webAPI.updaterecord
I am having issues with trying to access a pcf control using javascript "formContext.getControl"
In our project, I've developed a JavaScript function named "saveForm" intended to trigger the execution of the save functionality within the PCF control. To achieve this, I utilized the "formContext.getControl" method to obtain a reference to the PCF control instance.
Get the Pcf Control using javascript:
let control = formContext.getControl("lfs_pcfquestioninput");
javascript logic:
let control = formContext.getControl("lfs_pcfquestioninput");
// Call the updateControlPropertyWithValue method within the pcf control
control.updateControlPropertyWithValue(new Date());
Within the PCF control, I've implemented a method named "updateControlPropertyWithValue" to handle the saving functionality. This method is designed to update certain properties of the control based on user input or other factors.
However, upon attempting to execute the "updateControlPropertyWithValue" method using the provided logic, I encountered an issue. Specifically, the JavaScript code returned an error indicating that the "updateControlPropertyWithValue" method could not be found on the control instance.
Pcf Control Method
public async updateControlPropertyWithValue(propertyValue: Date Promise<void> {
try {
// Get the record ID from the context
const recordId = this._entityid;
const entityTypeName = this._entityTypeName;
// Construct the entity object with the property to update
const entityToUpdate: ComponentFramework.WebApi.Entity = {
lfs_pcfcontrolupdateon: propertyValue,
};
// Execute the request to update the record
await this._webAPI.updateRecord(entityTypeName, recordId, entityToUpdate);
// Log a message indicating successful property update
console.log("lfs_PcfControlUpdateOn property updated successfully.");
// Trigger the notifyOutputChanged method to mark the form as unsaved
this.notifyOutputChanged();
} catch (error) {
console.error("Error updating control property:", error);
}
}
I verified that the method is correctly implemented within the PCF control code and is properly exported for external access. Additionally, I ensured that the manifest file associated with the PCF control accurately specifies the method.
Despite these efforts, the error persists, leading me to believe there may be a discrepancy in how the method is being accessed or invoked from the JavaScript code.
Any suggestion on how I can resolve this issue?
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