cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Julien2
Kudo Kingpin
Kudo Kingpin

Dataset template debugging failure

Hello,

 

After creating a PCF using a dataset template, we are getting the below error when we try to debug/run the component:

Julien2_0-1669050379514.png

 

Screenshot 2022-11-21 210456.png

Any advice on what might be the issue and how to resolve it?

 

I would greatly appreciate any assistance.

Best regards,
Julien

2 ACCEPTED SOLUTIONS

Accepted Solutions
DianaBirkelbach
Most Valuable Professional
Most Valuable Professional

Hi @Julien2 ,

 

The linting rules were changed. To ignore that rules and go on with the development you can

1. locate the file ".eslintrc.json" in the root of your project, and inside that locate the "rules" node. There you can tuth "no-unused-vars" off. 

DianaBirkelbach_0-1669055233751.png

I this this is the reason: https://github.com/typescript-eslint/typescript-eslint/blob/main/docs/linting/TROUBLESHOOTING.md#i-g...

 

2. Didn't figured out why that "PropertyHelper" is not defined anymore, but you can disable the rule for that line

// eslint-disable-next-line no-undef
import DataSetInterfaces = ComponentFramework.PropertyHelper.DataSetApi;

 

After that you should be able to run the "npm run build"

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

Oh, just one more thing to add to what @DianaBirkelbach said: in addition to turning this rule off, you can also just set it to Warning so eslint still tells you when you've got unused vars, but it doesn't stop you from building.

"rules": {
    "no-unused-vars": ["warn"]
}

View solution in original post

12 REPLIES 12
DianaBirkelbach
Most Valuable Professional
Most Valuable Professional

Hi @Julien2 ,

 

The linting rules were changed. To ignore that rules and go on with the development you can

1. locate the file ".eslintrc.json" in the root of your project, and inside that locate the "rules" node. There you can tuth "no-unused-vars" off. 

DianaBirkelbach_0-1669055233751.png

I this this is the reason: https://github.com/typescript-eslint/typescript-eslint/blob/main/docs/linting/TROUBLESHOOTING.md#i-g...

 

2. Didn't figured out why that "PropertyHelper" is not defined anymore, but you can disable the rule for that line

// eslint-disable-next-line no-undef
import DataSetInterfaces = ComponentFramework.PropertyHelper.DataSetApi;

 

After that you should be able to run the "npm run build"

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."
cchannon
Multi Super User
Multi Super User

Yeah, in my opinion the no-unused-vars rule should not be enabled by default, but that's the way it is.

 

It applies to parameters in function signature as well, so even "state" in init is considered an unused var if you don't do something with it, which makes this a manual step you will have to take for the majority of all pcfs... annoying, but at least it isn't a big lift, and the eslint rule violations are pretty clear about what you need to fix, so could be much worse...

Oh, just one more thing to add to what @DianaBirkelbach said: in addition to turning this rule off, you can also just set it to Warning so eslint still tells you when you've got unused vars, but it doesn't stop you from building.

"rules": {
    "no-unused-vars": ["warn"]
}
Julien2
Kudo Kingpin
Kudo Kingpin

Hello again @DianaBirkelbach  @cchannon ,

 

Thank you for your assistance.

 

I applied what you mentioned and when I try to publish again I got the below errors:

 

[pcf-1065] [Error] ESLint validation error:
C:\Users\\Dev\ConvertPayComponent\ConvertPayComponent\component.tsx
    1:1   error    Definition for rule 'react/jsx-no-bind' was not found  react/jsx-no-bind
   51:5   warning  'Xrm' is not defined                                   no-undef
  122:15  warning  'Xrm' is not defined                                   no-undef
  122:75  warning  'Xrm' is not defined                                   no-undef
  134:5   warning  'Xrm' is not defined                                   no-undef
  164:9   warning  'Xrm' is not defined                                   no-undef

Any idea what should be added or changed?

 

Thank you!

DianaBirkelbach
Most Valuable Professional
Most Valuable Professional

Hi @Julien2 , 

 

Is this still the PCF  generated with the template? Have you added some code or configs?

I can build the new PCF created from the template. 
If you've changed the code a little, maybe you can provide the project ?
Otherwise maybe you can have a look to the changes ..?

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."
Julien2
Kudo Kingpin
Kudo Kingpin

Hello @DianaBirkelbach ,

Yes, the PCF was generated with the template without any code modifications, and the only thing that I modified is the ".eslintrc.json" based on what you mentioned.

 

Please find attached the PCF project which includes all the details including the CLI, Typescript, and the Node version we're using.

Kindly let me know what we are missing or doing wrong.

 

Awaiting your response.

 

Best regards,
Julien

There is no Xrm object in PCFs. That is only in Client form script. Whatever code you have in there using Xrm.<whatever> will not work. PCF does have its own web API object in context though. I suggest you read up on that here.

Hi @Julien2 , 

As I've guessed, your project is not the standard template anymore. The issues are with the code you've added.

So, to make it work you need to:

 - declare the "no-used-vars" : "off" inside the rules node of the .eslintrc.json (as posted above)

- As @cchannon posted, using the Xrm obejct inside a PCF is not allowed. Inside your project you need to change:

  • to get the userId use "context.userSettings.userId"
  • to work with webAPI you need to declare the the webAPI usage in the manifest. 
    <uses-feature name="WebAPI" required="true" />​
    then you'll have access to context.webAPI (inside the model-driven apps, including Custom Pages)
  • to use the navigation features, instead of Xrm.Navigation  declare the "uses-feature" Utility in the manifest (similar to webAPI)- Then you'll have access to context.navigation. I have here a blog about the ways to open a record: https://dianabirkelbach.wordpress.com/2020/10/09/dataset-pcf-using-fluentui-open-record/. There is also a dataset.openDatasetItem method.
  • that " 96:7 error Definition for rule 'react/jsx-no-bind' was not found react/jsx-no-bind" error seems to be caused by the eslint disable command (comment line inside select.tsx on line 96), inside the "select.tsx". By removing that I could build the project.,

To see all the context features, have a look to the context sdk: https://learn.microsoft.com/en-us/power-apps/developer/component-framework/reference/context?WT.mc_i...

 

Maybe it helps to add that the dataset PCF are able to get the date from the platform, and also to save the data using the save dataset methods. That way the requests are not hardcode inside the code, but the customizer can choose which table to use. That will also allow to interact with the ribbon.
So maybe you don't need all that webAPI requests.
For more info, here is my blog about the way to save the data: https://dianabirkelbach.wordpress.com/2021/12/20/editable-dataset-pcf-new-sdk-methods/

I have a blog series about implementing a dataset PCF, with links to further blogs on every subject: https://dianabirkelbach.wordpress.com/2020/10/09/dataset-pcf-using-fluentui-open-record/

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 @cchannon   ,

Thank you for your assistance.

I will just be using the Web API instead of XRM and follow the steps mentioned by Diana including the blog posts that I am always following up on. (Thank you for sharing such interesting content)

I just wanted to ask you regarding the Power Apps CLI version on how can I install a previous version of the CLI since I am not able to find it in the official microsoft docs:

https://learn.microsoft.com/en-us/power-platform/developer/cli/introduction

What is the command that should be executed to revert back to a previous CLI version?

Awaiting your response.

Best regards,

 Julien

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