Updated PCF Tooling version is now available (July 2019)!

[peterv333]

The updated version of PCF tooling (PowerApps CLI) is now available! We are excited to announce that the new version is offering an enhanced test harness UI and support for data-set control mock data input.  This release contains a number of other improvements too:

• Test harness now supports mock data-set inputs from a local CSV file. You can export mock data from any environment and use it in your inner developer loop to simulate data-set control behavior!
• Updated test harness UI which is now aligned with PowerApps UI theme and improved collapsible panes.
• We made the test harness UI more accessible to enable all developers
• The test harness now allows selection of different form factors (Web, Tablet, and Phone). This will enable you to test how your form-factor based implementation impacts control behavior. To take your local testing even further, we will also add the ability to manually adjust height & width in the coming release.
• There is now added support for PCF 'UsesFeature' capability in control manifest.
• We further made improvements in manifest validation for controls with datasets

Please make sure to update your Microsoft PowerApps CLI to the latest version and take advantage of all the latest capabilities by following the upgrade instructions. You can also find newly added features described in the updated documentation. 

If you have any questions please don’t hesitate to respond to this post.

[HansG]

I have a control which has a DateAndTime.DateOnly property as a binding and after updating the PCF Tooling to the latest version I get an error from React when the output of the control is returned:

react-dom.production.min.js:117 Invariant Violation: Minified React error #31; visit https://reactjs.org/docs/error-decoder.html?invariant=31&args[]=Tue%20Jan%2001%202019%2001%3A00%3A00... for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
at pb (http://127.0.0.1:8181/lib/react-dom.production.min.js:12:454)
at n (http://127.0.0.1:8181/lib/react-dom.production.min.js:13:221)
at Ac (http://127.0.0.1:8181/lib/react-dom.production.min.js:70:369)
at http://127.0.0.1:8181/lib/react-dom.production.min.js:80:190
at N (http://127.0.0.1:8181/lib/react-dom.production.min.js:89:471)
at hi (http://127.0.0.1:8181/lib/react-dom.production.min.js:105:408)
at Qg (http://127.0.0.1:8181/lib/react-dom.production.min.js:144:217)
at Rg (http://127.0.0.1:8181/lib/react-dom.production.min.js:145:76)
at Sc (http://127.0.0.1:8181/lib/react-dom.production.min.js:158:109)
at Z (http://127.0.0.1:8181/lib/react-dom.production.min.js:156:492)
at Kc (http://127.0.0.1:8181/lib/react-dom.production.min.js:155:52)
at ya (http://127.0.0.1:8181/lib/react-dom.production.min.js:153:159)
at Object.enqueueSetState (http://127.0.0.1:8181/lib/react-dom.production.min.js:202:409)
at t.setState (http://127.0.0.1:8181/lib/react.production.min.js:20:433)
at t.onOutputChange (http://127.0.0.1:8181/harness.js:11:278912)
at http://127.0.0.1:8181/harness.js:11:353259

With string outputs it works fine but seems something broke for Date output objects. Has anyone else encountered this issue and is there a solution?

[GregHurlmanMSFT]

@HansG -- can you clarify if this error happens when running the debug harness (the site you get when you run 'npm run start'), when hosted in a Model-Driven PowerApp/UCI App, or both?

[HansG]

@GregHurlmanMSFT it is when running in the debug harness.

[GregHurlmanMSFT]

@HansG Thanks for following up -- we're working on this issue now, and hope to have it fixed soon. If you run into this same issue when running your component in an actual app, please let us know.

[rexkenley]

I have the same issue. This was my workaround for the testing harness but then found out that I cannot update the date field properly when deployed.

  public getOutputs(): IOutputs {
    //@ts-ignore
    return { value: this.currentValue && this.currentValue.toString() };
  }

Is there a guide on how to properly return values based on the property of-type?

[rexkenley]

@GregHurlmanMSFT 

Is there an ETA on a fix for this issue? Thanks!