Calculated date field doesn´t get populated when pasting into another field

(0) Share

Report

Posted on by Markus_Benning

Hi all

My goal is to automatically update a date field by 1 year once a certain date has been reached.

Name of the field: Next review date (type: simple - date only)

To update it I´ve created another calculated field which takes the next review date and adds a year to it.

In the next step I´ve created a workflow which copies the "Next Review date Plus Year" value and paste it into "Next Review date" if certain conditions meet the requirements.

The workflow runs sucessefully but after it ran the next review date is blank.

What can I do?

Thank you very much ahead of time!

Btw. this is the whole workflow:

1. Workflow runs every day at 05:00 am

2. Graps information by fetch XML

3. Paste the calculated date into "Next Review date" field

Regards

Markus

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (7)

Answers (1)

Parvez Ghumra 1,579 Moderator on at

Like (0)

Report

@Markus_Benning What is the trigger of your Cloud Flow? Can you also share a screenshot of the logic of the Update action in your Cloud Flow in the designer

Was this reply helpful? Yes No
Markus_Benning 19 on at

Like (0)

Report

Done

Was this reply helpful? Yes No
Parvez Ghumra 1,579 Moderator on at

Like (0)

Report

@Markus_Benning What are the properties of your Compose action and what expression are you using to set the value of Next Review Date in your Update action?

Was this reply helpful? Yes No
Markus_Benning 19 on at

Like (0)

Report

The compose step fundementally doesn´t play no role I just tried if the the workflow works if I put the output of the fetch xml query into compose. I do not even use the compose values in the further setp.
Not sure if I understand you correctly. You want to know the expressions that I use to check if conditions are met? If that´s the case I only grap those records which do meet the following requirements that way:

<fetch version="1.0" output-format="xml-platform" mapping="logical" distinct="false">
<entity name="car_contracts">
<attribute name="car_contractsid" />
<attribute name="car_contractname" />
<attribute name="createdon" />
<order attribute="car_contractname" descending="false" />
<filter type="and">
<filter type="and">
<condition attribute="car_nextreviewdate" operator="last-seven-days" />
<condition attribute="statecode" operator="eq" value="0" />
</filter>
</filter>
</entity>
</fetch>

The logic is that for each record which matches the above criteria the next review date gets updated.
If that´s not your question please let me know.

Was this reply helpful? Yes No
mjburley 370 on at

Like (0)

Report

I fell into exactly the same trap a couple of weeks back using a fetchXML query.

You do not name the "car_nextreviewdate" as one of the attributes to return, it's just used in the filter!

Just add the line
<attribute name="car_nextreviewdate" />

Was this reply helpful? Yes No
Markus_Benning 19 on at

Like (0)

Report

Unfortunately that did not work for me. However, I´ve now solved it with Compose. Thank you for you help!

Was this reply helpful? Yes No
Verified answer

Markus_Benning 19 on at

Like (1)

Report

I solved the issue by using compose function.
Now the date gets populated in the required field.
This was obviously a format issue.

Was this reply helpful? Yes No