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

Uncaught PCFNonImplementedError: retrieveMultipleRecords: Method not implemented

Hi,

I have completed this tutorial: Use the Microsoft Dataverse web API in a Power Apps component.

I am testing the web API functionality

I published and hosted the component in my Microsoft Power Platform environment. 

 

I hosted the component as follows:

  • https://make.powerapps.com/
  • Create
  • Start from a Dataverse table 
  • Connect to my custom table (I plan on using later)
  • Import the custom component
  • Add it to a new screen

The component displays, but If I click any of the buttons that call WebAPI methods, I get an error like this:

 

Uncaught PCFNonImplementedError: retrieveMultipleRecords: Method not implemented

 


I added the WebAPI feature to my `ControlManifest.xml` file:

 

        <feature-usage>
            <uses-feature name="WebAPI" required="true" />
        </feature-usage>
    </control>

 



Why is the method not recognized? Is it because the screen is a canvas?

How do I add a custom component to a Power Apps app that can use the WebAPI? 



 

1 ACCEPTED SOLUTION

Accepted Solutions
a33ik
Most Valuable Professional
Most Valuable Professional

It took some time to understand what issues you experienced.

PCF control won't have Webapi capabilities when it will be used from Canvas Apps itself. So your number 1 is valid.

Now to custom pages - 2 and 3. It won't work when it is used from make.powerapps.com but once the page is published and opened from a context of Dynamics application - it should start working.

View solution in original post

6 REPLIES 6
a33ik
Most Valuable Professional
Most Valuable Professional

Hello,

Where are you trying to use this PCF control? I will work in the Model Driven App or Custom Page but not in pure Canvas App.

MattDC
Frequent Visitor

I've tried in three places. I'm not sure where to add my custom component that can use the WebAPI feature to access Dataverse. 

 

One:

 

  • https://make.powerapps.com/
  • Start from Dataverse. Start from a Dataverse table to create a three screen app
  • Connect to my Microsoft Dataverse table - tests (custom table)
  • Tree View > Components > Import Components > Code > Import my custom component
  • Insert > Code Components > my custom component
  • Click "Create record with revenue of 100" button

I then get an error:

createRecord: Method not implemented

 

Two

 

  • https://make.powerapps.com
  • Create
  • Start from Blank App
  • Blank App based on Dataverse > Create
  • Pages > New button > Custom Page > Create a new custom page 
  • Insert > Get More components button > Import Components - Code > Import custom component
  • Insert > Code components > Custom component
  • Click "Create record with revenue of 100" button

I then get an error:

createRecord: Method not implemented

 

Three

 

  • https://make.powerapps.com
  • Create
  • Start from Blank App
  • Blank App based on Dataverse > Create
  • Pages > New button > Custom Page > Use an existing custom page > Dataverse Actions Page > Add
  • Edit Custom Page > Unsaved Changes > Save and continue
  • Pop-up message: This page may contain unsafe code > Open app
  • Insert > Get More components button > Import Components - Code > Import custom component
  • Insert > Classic tab > Code components > Custom component
  • Click "Create record with revenue of 100" button

I then get an error:

 

createRecord: Method not implemented

 

Do I need to upload my component as a Solution file?

I use the following commands to upload my component to the PowerApps platform: 

 

npm run build
pac pcf push --publisher-prefix msl

 

I logged in to PowerApps using my Microsoft 365 trial developer subscription, I'm not sure if that is an issue. 

MattDC
Frequent Visitor

Here's some of my code:

ControlManifest.Input.xml:

 

<?xml version="1.0" encoding="utf-8"?>
<manifest>
    <control namespace="webapi" constructor="TSWebAPI" version="1.0.1" display-name-key="TS_WebAPI_Display_Key" description-key="TS_WebAPI_Desc_Display_Key" control-type="standard">
        <property name="stringProperty" display-name-key="stringProperty_Display_Key" description-key="stringProperty_Desc_Key" of-type="SingleLine.Text" usage="bound" required="true" />
        <resources>
            <code path="index.ts" order="1" />
            <css path="css/TS_WebAPI.css" order="2" />
        </resources>
        <feature-usage>
            <uses-feature name="WebAPI" required="true" />
        </feature-usage>
    </control>
</manifest>

 

 

index.ts:

 

import { IInputs, IOutputs } from "./generated/ManifestTypes";

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

// Reference to the control container HTMLDivElement
// This element contains all elements of our custom control example
private _container: HTMLDivElement;

// Reference to ComponentFramework Context object
private _context: ComponentFramework.Context<IInputs>;

// Flag if control view has been rendered
private _controlViewRendered: Boolean;

// References to button elements that are rendered by example custom control
private _createEntity1Button: HTMLButtonElement;
private _createEntity2Button: HTMLButtonElement;
private _createEntity3Button: HTMLButtonElement;
private _deleteRecordButton: HTMLButtonElement;
private _fetchXmlRefreshButton: HTMLButtonElement;
private _oDataRefreshButton: HTMLButtonElement;

// References to div elements that are rendered by the example custom control
private _odataStatusContainerDiv: HTMLDivElement;
private _resultContainerDiv: HTMLDivElement;

// Name of entity to use for example Web API calls that are performed by this control
private static _entityName: string = "account";

// Required field on _entityName of type 'single line of text'
// Example Web API calls that are performed by the example custom control will set this field for new record creation examples
private static _requiredAttributeName: string = "name";

// Value that the _requiredAttributeName field will be set to for new created records
private static _requiredAttributeValue: string = "Web API Custom Control (Sample)";

// Name of currency field on _entityName to populate during record create
// Example Web API calls that are performed by the example custom control will set and read this field
private static _currencyAttributeName: string = "revenue";

// Friendly name of currency field (only used for control UI - no functional impact)
private static _currencyAttributeNameFriendlyName: string = "annual revenue";

/**
 * Empty constructor.
 */
constructor() {

}

/**
 * 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.
 *  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.
 *  notifyOutputChanged A callback method to alert the framework that the control has new outputs ready to be retrieved asynchronously.
 *  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.
 *  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): void {
    this._context = context;
    this._controlViewRendered = false;
    this._container = document.createElement("div");
    this._container.classList.add("TSWebAPI_Container");
    container.appendChild(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.
 *  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 {
    if (!this._controlViewRendered) {
        this._controlViewRendered = true;

        // Render Web API Examples
        this.renderCreateExample();
        this.renderDeleteExample();
        this.renderFetchXmlRetrieveMultipleExample();
        this.renderODataRetrieveMultipleExample();

        // Render result div to display output of Web API calls
        this.renderResultsDiv();}
}

/**
 * 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 {
    return {};
}

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

/**
 * Helper method to create HTML button that is used for CreateRecord Web API Example
 *  buttonLabel : Label for button
 *  buttonId : ID for button
 *  buttonValue : Value of button (attribute of button)
 *  onClickHandler : onClick event handler to invoke for the button
 */
 private createHTMLButtonElement(buttonLabel: string, buttonId: string, buttonValue: string | null, onClickHandler: (event?: any) => void): HTMLButtonElement {
    let button: HTMLButtonElement = document.createElement("button");
    button.innerHTML = buttonLabel;

    if (buttonValue) {
        button.setAttribute("buttonvalue", buttonValue);
    }

    button.id = buttonId;

    button.classList.add("SampleControl_WebAPI_ButtonClass");
    button.addEventListener("click", onClickHandler);
    return button;
}

/**
 * Helper method to create HTML Div Element
 *  elementClassName : Class name of div element
 *  isHeader : True if 'header' div - adds extra class and post-fix to ID for header elements
 *  innerText : innerText of Div Element
 */
private createHTMLDivElement(elementClassName: string, isHeader: Boolean, innerText?: string): HTMLDivElement {
    let div: HTMLDivElement = document.createElement("div");

    if (isHeader) {
        div.classList.add("SampleControl_WebAPI_Header");
        elementClassName += "_header";
    }

    if (innerText) {
        div.innerText = innerText.toUpperCase();
    }

    div.classList.add(elementClassName);
    return div;
}

/** 
* Renders a 'result container' div element to inject the status of the example Web API calls 
*/
private renderResultsDiv() {
    // Render header label for result container
    let resultDivHeader: HTMLDivElement = this.createHTMLDivElement("result_container", true,
        "Result of last action");
    this._container.appendChild(resultDivHeader);

    // Div elements to populate with the result text
    this._resultContainerDiv = this.createHTMLDivElement("result_container", false, undefined);
    this._container.appendChild(this._resultContainerDiv);

    // Init the result container with a notification that the control was loaded
    this.updateResultContainerText("Web API sample custom control loaded");
}

/**
* Helper method to inject HTML into result container div
*  statusHTML : HTML to inject into result container
*/
private updateResultContainerText(statusHTML: string): void {
    if (this._resultContainerDiv) {
        this._resultContainerDiv.innerHTML = statusHTML;
    }
}

/**
 * Helper method to inject error string into result container div after failed Web API call
 *  errorResponse : error object from rejected promise
 */
private updateResultContainerTextWithErrorResponse(errorResponse: any): void {
    if (this._resultContainerDiv) {
        // Retrieve the error message from the errorResponse and inject into the result div
        let errorHTML: string = "Error with Web API call:";
        errorHTML += "<br />"
        errorHTML += errorResponse.message;
        this._resultContainerDiv.innerHTML = errorHTML;
    }
}

/**
* Helper method to generate Label for Create Buttons
*  entityNumber : value to set _currencyAttributeNameFriendlyName field to for this button
*/
private getCreateRecordButtonLabel(entityNumber: string): string {
    return "Create record with " + TSWebAPI._currencyAttributeNameFriendlyName + " of " + entityNumber;
}

/**
* Helper method to generate ID for Create button
*  entityNumber : value to set _currencyAttributeNameFriendlyName field to for this button
*/
private getCreateButtonId(entityNumber: string): string {
    return "create_button_" + entityNumber;
}

/**
* Event Handler for onClick of create record button
*  event : click event
*/
private createButtonOnClickHandler(event: Event): void {
    // Retrieve the value to set the currency field to from the button's attribute
    let currencyAttributeValue: Number = parseInt(
        (event.srcElement! as Element)!.attributes.getNamedItem("buttonvalue")!.value
    );

    // Generate unique record name by appending timestamp to _requiredAttributeValue
    let recordName: string = TSWebAPI._requiredAttributeValue + "_" + Date.now();

    // Set the values for the attributes we want to set on the new record
    // If you want to set additional attributes on the new record, add to data dictionary as key/value pair
    var data: any = {};
    data[TSWebAPI._requiredAttributeName] = recordName;
    data[TSWebAPI._currencyAttributeName] = currencyAttributeValue;

    // store reference to 'this' so it can be used in the callback method
    var thisRef = this;

    // Invoke the Web API to create the new record
    this._context.webAPI.createRecord(TSWebAPI._entityName, data).then(
        function (response: ComponentFramework.LookupValue) {
            // Callback method for successful creation of new record

            // Get the ID of the new record created
            let id: string = response.id;

            // Generate HTML to inject into the result div to showcase the fields and values of the new record that is created
            let resultHtml: string = "Created new " + TSWebAPI._entityName + " record with below values:"
            resultHtml += "<br />";
            resultHtml += "<br />";
            resultHtml += "id: " + id;
            resultHtml += "<br />";
            resultHtml += "<br />";
            resultHtml += TSWebAPI._requiredAttributeName + ": " + recordName;
            resultHtml += "<br />";
            resultHtml += "<br />";
            resultHtml += TSWebAPI._currencyAttributeName + ": " + currencyAttributeValue;

            thisRef.updateResultContainerText(resultHtml);
        },
        function (errorResponse: any) {
            // Error handling code here - record failed to be created
            thisRef.updateResultContainerTextWithErrorResponse(errorResponse);
        }
    );
}

/**
* Event Handler for onClick of delete record button
*  event : click event
*/
private deleteButtonOnClickHandler(): void {
    // Invoke a lookup dialog to allow the user to select an existing record of type _entityName to delete
    var lookUpOptions: any =
    {
        entityTypes: [TSWebAPI._entityName]
    };

    // store reference to 'this' so it can be used in the callback method
    var thisRef = this;

    var lookUpPromise: any = this._context.utils.lookupObjects(lookUpOptions);

    lookUpPromise.then(
        // Callback method - invoked after user has selected an item from the lookup dialog
        // Data parameter is the item selected in the lookup dialog
        (data: ComponentFramework.EntityReference[]) => {
            if (data && data[0]) {
                // Get the ID and entityType of the record that was selected by the lookup
                let id: string = data[0].id.guid;
                let entityType: string = data[0].etn!;

                // Invoke the deleteRecord method of the WebAPI to delete the selected record
                this._context.webAPI.deleteRecord(entityType, id).then(
                    function (response: ComponentFramework.LookupValue) {
                        // Record was deleted successfully
                        let responseId: string = response.id;
                        let responseEntityType: string = response.name!;

                        // Generate HTML to inject into the result div to showcase the deleted record 
                        thisRef.updateResultContainerText("Deleted " + responseEntityType + " record with ID: " + responseId);
                    },
                    function (errorResponse: any) {
                        // Error handling code here
                        thisRef.updateResultContainerTextWithErrorResponse(errorResponse);
                    }
                );
            }
        },
        (error: any) => {
            // Error handling code here
            thisRef.updateResultContainerTextWithErrorResponse(error);
        }
    );
}

/**
* Event Handler for onClick of calculate average value button
*  event : click event
*/
private calculateAverageButtonOnClickHandler(): void {
    // Build FetchXML to retrieve the average value of _currencyAttributeName field for all _entityName records
    // Add a filter to only aggregate on records that have _currencyAttributeName not set to null
    let fetchXML: string = "<fetch distinct='false' mapping='logical' aggregate='true'>";
    fetchXML += "<entity name='" + TSWebAPI._entityName + "'>";
    fetchXML += "<attribute name='" + TSWebAPI._currencyAttributeName + "' aggregate='avg' alias='average_val' />";
    fetchXML += "<filter>";
    fetchXML += "<condition attribute='" + TSWebAPI._currencyAttributeName + "' operator='not-null' />";
    fetchXML += "</filter>";
    fetchXML += "</entity>";
    fetchXML += "</fetch>";

    // store reference to 'this' so it can be used in the callback method
    var thisRef = this;

    // Invoke the Web API RetrieveMultipleRecords method to calculate the aggregate value
    this._context.webAPI.retrieveMultipleRecords(TSWebAPI._entityName, "?fetchXml=" + fetchXML).then(
        function (response: ComponentFramework.WebApi.RetrieveMultipleResponse) {
            // Retrieve multiple completed successfully -- retrieve the averageValue 
            let averageVal: Number = response.entities[0].average_val;

            // Generate HTML to inject into the result div to showcase the result of the RetrieveMultiple Web API call
            let resultHTML: string = "Average value of " + TSWebAPI._currencyAttributeNameFriendlyName + " attribute for all " + TSWebAPI._entityName + " records: " + averageVal;
            thisRef.updateResultContainerText(resultHTML);
        },
        function (errorResponse: any) {
            // Error handling code here
            thisRef.updateResultContainerTextWithErrorResponse(errorResponse);
        }
    );
}

/**
* Event Handler for onClick of calculate record count button
*  event : click event
*/
private refreshRecordCountButtonOnClickHandler(): void {
    // Generate OData query string to retrieve the _currencyAttributeName field for all _entityName records
    // Add a filter to only retrieve records with _requiredAttributeName field which contains _requiredAttributeValue
    let queryString: string = "?$select=" + TSWebAPI._currencyAttributeName + "&$filter=contains(" + TSWebAPI._requiredAttributeName +
        ",'" + TSWebAPI._requiredAttributeValue + "')";

    // store reference to 'this' so it can be used in the callback method
    var thisRef = this;

    // Invoke the Web API Retrieve Multiple call
    this._context.webAPI.retrieveMultipleRecords(TSWebAPI._entityName, queryString).then(
        function (response: any) {
            // Retrieve Multiple Web API call completed successfully
            let count1: number = 0;
            let count2: number = 0;
            let count3: number = 0;

            // Loop through each returned record
            for (let entity of response.entities) {
                // Retrieve the value of _currencyAttributeName field
                let value: Number = entity[TSWebAPI._currencyAttributeName];

                // Check the value of _currencyAttributeName field and increment the correct counter
                if (value == 100) {
                    count1++;
                }
                else if (value == 200) {
                    count2++;
                }
                else if (value == 300) {
                    count3++;
                }
            }

            // Generate HTML to inject into the fetch xml status div to showcase the results of the OData retrieve example
            let innerHtml: string = "Use above buttons to create or delete a record to see count update";
            innerHtml += "<br />";
            innerHtml += "<br />";
            innerHtml += "Count of " + TSWebAPI._entityName + " records with " + TSWebAPI._currencyAttributeName + " of 100: " + count1;
            innerHtml += "<br />";
            innerHtml += "Count of " + TSWebAPI._entityName + " records with " + TSWebAPI._currencyAttributeName + " of 200: " + count2;
            innerHtml += "<br />";
            innerHtml += "Count of " + TSWebAPI._entityName + " records with " + TSWebAPI._currencyAttributeName + " of 300: " + count3;

            // Inject the HTML into the fetch xml status div
            if (thisRef._odataStatusContainerDiv) {
                thisRef._odataStatusContainerDiv.innerHTML = innerHtml;
            }

            // Inject a success message into the result div
            thisRef.updateResultContainerText("Record count refreshed");
        },
        function (errorResponse: any) {
            // Error handling code here
            thisRef.updateResultContainerTextWithErrorResponse(errorResponse);
        }
    );
}

/** 
* Renders example use of CreateRecord Web API
*/
private renderCreateExample() {
    // Create header label for Web API sample
    let headerDiv: HTMLDivElement = this.createHTMLDivElement("create_container", true, "Click to create "
        + TSWebAPI._entityName + " record");
    this._container.appendChild(headerDiv);

    // Create button 1 to create a record with the revenue field set to 100
    let value1: string = "100";
    this._createEntity1Button = this.createHTMLButtonElement(
        this.getCreateRecordButtonLabel(value1),
        this.getCreateButtonId(value1),
        value1,
        this.createButtonOnClickHandler.bind(this));

    // Create button 2 to create a record with the revenue field set to 200
    let value2: string = "200";
    this._createEntity2Button = this.createHTMLButtonElement(
        this.getCreateRecordButtonLabel(value2),
        this.getCreateButtonId(value2),
        value2,
        this.createButtonOnClickHandler.bind(this));

    // Create button 3 to create a record with the revenue field set to 300
    let value3: string = "300";
    this._createEntity3Button = this.createHTMLButtonElement(
        this.getCreateRecordButtonLabel(value3),
        this.getCreateButtonId(value3),
        value3,
        this.createButtonOnClickHandler.bind(this));

    // Append all button HTML elements to custom control container div
    this._container.appendChild(this._createEntity1Button);
    this._container.appendChild(this._createEntity2Button);
    this._container.appendChild(this._createEntity3Button);
}

/** 
* Renders example use of DeleteRecord Web API
*/
private renderDeleteExample(): void {
    // Create header label for Web API sample
    let headerDiv: HTMLDivElement = this.createHTMLDivElement("delete_container", true, "Click to delete " + TSWebAPI._entityName + " record");

    // Render button to invoke DeleteRecord Web API call
    this._deleteRecordButton = this.createHTMLButtonElement(
        "Select record to delete",
        "delete_button",
        null,
        this.deleteButtonOnClickHandler.bind(this));

    // Append elements to custom control container div
    this._container.appendChild(headerDiv);
    this._container.appendChild(this._deleteRecordButton);
}

/** 
* Renders example use of RetrieveMultiple Web API with OData
*/
private renderODataRetrieveMultipleExample(): void {
    let containerClassName: string = "odata_status_container";

    // Create header label for Web API sample
    let statusDivHeader: HTMLDivElement = this.createHTMLDivElement(containerClassName, true, "Click to refresh record count");
    this._odataStatusContainerDiv = this.createHTMLDivElement(containerClassName, false, undefined);

    // Create button to invoke OData RetrieveMultiple Example
    this._fetchXmlRefreshButton = this.createHTMLButtonElement(
        "Refresh record count",
        "odata_refresh",
        null,
        this.refreshRecordCountButtonOnClickHandler.bind(this));

    // Append HTML elements to custom control container div
    this._container.appendChild(statusDivHeader);
    this._container.appendChild(this._odataStatusContainerDiv);
    this._container.appendChild(this._fetchXmlRefreshButton);
}

/** 
* Renders example use of RetrieveMultiple Web API with Fetch XML
*/
private renderFetchXmlRetrieveMultipleExample(): void {
    let containerName: string = "fetchxml_status_container";

    // Create header label for Web API sample
    let statusDivHeader: HTMLDivElement = this.createHTMLDivElement(containerName, true,
        "Click to calculate average value of " + TSWebAPI._currencyAttributeNameFriendlyName);
    let statusDiv: HTMLDivElement = this.createHTMLDivElement(containerName, false, undefined);

    // Create button to invoke Fetch XML RetrieveMultiple Web API example
    this._oDataRefreshButton = this.createHTMLButtonElement(
        "Calculate average value of " + TSWebAPI._currencyAttributeNameFriendlyName,
        "odata_refresh",
        null,
        this.calculateAverageButtonOnClickHandler.bind(this));

    // Append HTML Elements to custom control container div
    this._container.appendChild(statusDivHeader);
    this._container.appendChild(statusDiv);
    this._container.appendChild(this._oDataRefreshButton);
}}

 

 

 

 

a33ik
Most Valuable Professional
Most Valuable Professional

It took some time to understand what issues you experienced.

PCF control won't have Webapi capabilities when it will be used from Canvas Apps itself. So your number 1 is valid.

Now to custom pages - 2 and 3. It won't work when it is used from make.powerapps.com but once the page is published and opened from a context of Dynamics application - it should start working.

DianaBirkelbach
Most Valuable Professional
Most Valuable Professional

Hi @MattDC , 
@ totally agree with @a33ik . I would add to his solution , that if you need to work in Custom Pages, in order to be able to use the PCF in the designer, you can catch the error and provide some dummy fallback data. Then you could make the rest of the work in the designer. Something like this:

 

export const fetchRecords = async (....){
 try{    
    await webAPI.retrieveMultipleRecords(...)
  }
 catch(e){
        if(e instanceof Error){
            if(e.name === "PCFNonImplementedError"){
                return [] //your fallback data for the designer
            }
        }
        throw e;
    }

 

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."
MattDC
Frequent Visitor

Thanks! IT worked when I created a custom page in a Blank App based on Dataverse and published the app. I did not realize that you can't use the WebAPI when editing a custom page.

Helpful resources

Announcements

Update! June 13th, Community Ambassador Call for User Group Leaders and Super Users

Calling all Super Users & User Group Leaders     UPDATE:  We just wrapped up June's Community Ambassador monthly calls for Super Users and User Group Leaders. We had a fantastic call with lots of engagement. We are excited to share some highlights with you!    Big THANK YOU to our special guest Thomas Verhasselt, from the Copilot Studio Product Team for sharing how to use Power Platform Templates to achieve next generation growth.     A few key takeaways: Copilot Studio Cookbook Challenge:  Week 1 results are posted, Keep up the great work!Summer of Solutions:  Starting on Monday, June 17th. Just by providing solutions in the community, you can be entered to win tickets to Power Platform Community Conference.Super User Season 2: Coming SoonAll communities moving to the new platform end of July We also honored two different community members during the call, Mohamed Amine Mahmoudi and Markus Franz! We are thankful for both leaders' contributions and engagement with their respective communities. 🎉   Be sure to mark your calendars and register for the meeting on July 11th and stay up to date on all of the changes that are coming. Check out the Super User Forum boards for details.   We're excited to connect with you and continue building a stronger community together.   See you at the call!  

Win free tickets to the Power Platform Conference | Summer of Solutions

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

Copilot Cookbook Challenge | Week 2 Results | Win Tickets to the Power Platform Conference

We are excited to announce the "The Copilot Cookbook Community Challenge is a great way to showcase your creativity and connect with others. Plus, you could win tickets to the Power Platform Community Conference in Las Vegas in September 2024 as an amazing bonus.   Two ways to enter: 1. Copilot Studio Cookbook Gallery: https://aka.ms/CS_Copilot_Cookbook_Challenge 2. Power Apps Copilot Cookbook Gallery: https://aka.ms/PA_Copilot_Cookbook_Challenge   There will be 5 chances to qualify for the final drawing: Early Bird Entries: March 1 - June 2Week 1: June 3 - June 9Week 2: June 10 - June 16Week 3: June 17 - June 23Week 4: June 24 - June 30     At the end of each week, we will draw 5 random names from every user who has posted a qualifying Copilot Studio template, sample or demo in the Copilot Studio Cookbook or a qualifying Power Apps Copilot sample or demo in the Power Apps Copilot Cookbook. Users who are not drawn in a given week will be added to the pool for the next week. Users can qualify more than once, but no more than once per week. Four winners will be drawn at random from the total qualifying entrants. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once. If they are drawn multiple times, another user will be drawn at random. Prizes:  One Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value, does not include travel, lodging, or any other expenses) Winners are also eligible to do a 10-minute presentation of their demo or solution in a community solutions showcase at the event. To qualify for the drawing, templates, samples or demos must be related to Copilot Studio or a Copilot feature of Power Apps, Power Automate, or Power Pages, and must demonstrate or solve a complete unique and useful business or technical problem. Power Automate and Power Pagers posts should be added to the Power Apps Cookbook. Final determination of qualifying entries is at the sole discretion of Microsoft. Weekly updates and the Final random winners will be posted in the News & Announcements section in the communities on July 29th, 2024. Did you submit entries early?  Early Bird Entries March 1 - June 2:  If you posted something in the "early bird" time frame complete this form: https://aka.ms/Copilot_Challenge_EarlyBirds if you would like to be entered in the 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. Copilot Cookbook Gallery:Power Apps Cookbook Gallery:1.  @Mathieu_Paris 1.   @SpongYe 2.  @Dhanush 2.   @Deenuji 3.  n/a3.   @Nived_Nambiar  4.  n/a4.   @ManishSolanki 5.  n/a5.    n/a   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. Copilot Cookbook Gallery:Power Apps Cookbook Gallery:1. Kasun_Pathirana1. ManishSolanki2. cloudatica2. madlad3. n/a3. SpongYe4. n/a4. n/a5. n/a5. n/a

Celebrating the June Super User of the Month: Markus Franz

Markus Franz is a phenomenal contributor to the Power Apps Community. Super Users like Markus inspire others through their example, encouragement, and active participation.    The Why: "I do this to help others achieve what they are trying to do. As a total beginner back then without IT background I know how overwhelming things can be, so I decided to jump in and help others. I also do this to keep progressing and learning myself." Thank you, Markus Franz, for your outstanding work! Keep inspiring others and making a difference in the community! 🎉  Keep up the fantastic work! 👏👏   Markus Franz | LinkedIn  Power Apps: mmbr1606  

Your Moment to Shine: 2024 PPCC’s Got Power Awards Show

For the third year, we invite you, our talented community members, to participate in the grand 2024 Power Platform Community Conference's Got Power Awards. This event is your opportunity to showcase solutions that make a significant business impact, highlight extensive use of Power Platform products, demonstrate good governance, or tell an inspirational story. Share your success stories, inspire your peers, and show off some hidden talents.  This is your time to shine and bring your creations into the spotlight!  Make your mark, inspire others and leave a lasting impression. Sign up today for a chance to showcase your solution and win the coveted 2024 PPCC’s Got Power Award. This year we have three categories for you to participate in: Technical Solution Demo, Storytelling, and Hidden Talent.      The Technical solution demo category showcases your applications, automated workflows, copilot agentic experiences, web pages, AI capabilities, dashboards, and/or more. We want to see your most impactful Power Platform solutions!  The Storytelling category is where you can share your inspiring story, and the Hidden Talent category is where your talents (such as singing, dancing, jump roping, etc.) can shine! Submission Details:  Fill out the submission form https://aka.ms/PPCCGotPowerSignup by July 12th with details and a 2–5-minute video showcasing your Solution impact. (Please let us know you're coming to PPCC, too!)After review by a panel of Microsoft judges, the top storytellers will be invited to present a virtual demo presentation to the judges during early August. You’ll be notified soon after if you have been selected as a finalist to share your story live at PPCC’s Got Power!  The live show will feature the solution demos and storytelling talents of the top contestants, winner announcements, and the opportunity to network with your community.  It's not just a showcase for technical talent and storytelling showmanship, show it's a golden opportunity to make connections and celebrate our Community together! Let's make this a memorable event! See you there!   Mark your calendars! Date and Time: Thursday, Sept 19th Location: PPCC24 at the MGM Grand, Las Vegas, NV 

Tuesday Tip | Accepting Solutions

It's time for another TUESDAY TIPS, your weekly connection with the most insightful tips and tricks that empower both newcomers and veterans in the Power Platform Community! Every Tuesday, we bring you a curated selection of the finest advice, distilled from the resources and tools in the Community. Whether you’re a seasoned member or just getting started, Tuesday Tips are the perfect compass guiding you across the dynamic landscape of the Power Platform Community.   To enhance our collaborative environment, it's important to acknowledge when your question has been answered satisfactorily. Here's a quick guide on how to accept a solution to your questions: Find the Helpful Reply: Navigate to the reply that has effectively answered your question.Accept as Solution: Look for the "Accept as Solution" button or link, usually located at the bottom of the reply.Confirm Your Selection: Clicking this button may prompt you for confirmation. Go ahead and confirm that this is indeed the solution.Acknowledgment: Once accepted, the reply will be highlighted, and the original post will be marked as "Solved". This helps other community members find the same solution quickly. By marking a reply as an accepted solution, you not only thank the person who helped you but also make it easier for others with similar questions to find answers. Let's continue to support each other by recognizing helpful contributions. 

Users online (3,789)