Answered

Binding to a date attribute

(0) Share

Report

Posted on by Community Power Pla... Microsoft Employee

Hi guys,

Can you give me an example manifest file for binding to a DateTime field?

I've tried the following manifest file and it comes up with compile error :
" [tsl] ERROR in C:\PCF_Controls\_PCF\CountDownTimer\CountDownTimer\index.ts(231,4)
TS2322: Type 'string' is not assignable to type 'Date | undefined'."

<?xml version="1.0" encoding="utf-8" ?>
<manifest>
 <control namespace="ControlsAndrewLy" constructor="CountDownTimer" version="0.0.1" display-name-key="Countdown Timer Control" 
 description-key="A simple countdown timer, takes a date as an input" control-type="standard">
 
 <!-- property node identifies a specific, configurable piece of data that the control expects from CDS -->
 <property name="inputDate" display-name-key="Input Date" description-key="Input Date to be used for the countdown timer."
 of-type="DateAndTime.DateOnly" usage="bound" required="true" />

 <resources>
 <code path="index.ts" order="1"/>
 
 <css path="css/CountDownTimer.css" order="1" />
 <!-- UNCOMMENT TO ADD MORE RESOURCES
 <resx path="strings/CountDownTimer.1033.resx" version="1.0.0" />
 -->
 </resources>
 </control>

Following the docs online

https://docs.microsoft.com/en-us/powerapps/developer/component-framework/manifest-schema-reference/property#remarks

I am using DateAndTime.DateOnly should be an acceptable parameter of of-type?

Categories:

Power Apps Pro Dev & ISV

I have the same question (0)

All responses (9)

Answers (2)

Sort by

Hemant Gaur Microsoft Employee on at

Like (1)

Report
Copy link

Link copied!

this looks like the error when the value is used in the control implementation.

this.context.parameters.inputDate.raw is the Date object and can be used as date.getTime() or toString();

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

You're right hemant. Thanks for that again, fixed the reference in index.ts and that allows me to compile.

Although, now i have another issue, i've tried using the control against the Date of Birth field on contact and the control isn't showing up (using same manifest as above).

Was this reply helpful? Yes No
Hemant Gaur Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!
Not sure what might be happening here, but can you try using type-group and declaring contol support for both date and dateAndTime.

See example below

<type-group name="date"> <type>DateAndTime.DateOnly</type> <type>DateAndTime.DateAndTime</type> </type-group> <property name="value" display-name-key="DateTimeControl" description-key="DateTimeControl description" of-type-group="date" usage="bound" required="true" hidden="true" />

Was this reply helpful? Yes No
Verified answer

Community Power Pla... Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!
Hey Hemant, tried the above code within manifest. Still no go either.. not showing up as selectable control for birthdate field.

 <property name="inputDate" display-name-key="Input Date" description-key="Input Date to be used for the countdown timer." of-type-group="date" usage="bound" required="true" hidden="true" /> <type-group name="date"> <type>DateAndTime.DateOnly</type> <type>DateAndTime.DateAndTime</type> </type-group>

Was this reply helpful? Yes No
Hemant Gaur Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!
My Bad , please remove the following from xml.

hidden="true" />

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Still same result. Not showing up on date field.

Want to try it out on your environment?
https://1drv.ms/u/s!Ags-1oGgNllShd9ED5MirzwN4LIVQw?e=CbquI7

Was this reply helpful? Yes No
Verified answer

jolake Microsoft Employee on at

Like (1)

Report
Copy link

Link copied!

Hi Andrew,

I was able to import your control as is without issue on my machine (see attached). It shows up in the list for a control of DateTime.DateAndTime type.

I believe the issue may be that you have not updated the control version in the manifest when you made the change to remove the hidden="true" attribute on the property node, so those changes were not consumed when you imported the updated control manifest. The version in the solution you provided still shows 0.0.1, try re-importing after bumping that value and see if that fixes your issue.

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Ah, you're right, it was the version number. Thought it would overwrite my customisations when I import. Thanks for steering me in the right direction.

btw, guys i'm putting together a tips and tricks article for people getting started in PCF development. It's open source so if anyone has any tips they'd like to share to edit the following:
https://github.com/365lyf/PCFControls/blob/master/README.md

Was this reply helpful? Yes No
Hemant Gaur Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Customizations are always maintained when the new control version is published however control should adhere to the properties declared. For example if the new version of the control removes a required property , import is blocked at that time because there isnt a way to determine how the already configured property can be handled. New properties however can be added to the control and configurations are maintained . For development workflow, if at any point the situation arises which is very much possible to change the properties or their types, you can remove the configuration and then uninstall the previous control version.

Was this reply helpful? Yes No