Plain Text Content Control as Currency

[Jason_Collet]

Greetings,

After watching this video...

https://flow.microsoft.com/en-us/blog/intermediate-flow-of-the-week-create-pdf-invoices-using-word-t...
...I became inspired, and started working on a Flow that would generate Purchase Order Requests.  Following the instructions as per the video, I've created a Word Document with several Plain Text Content Controls:



Everything goes as planned until we hit the first entry that I need formatted as currency.  In the example above, the entry for "Price1" will not allow me to have a floating zero..."43.60" immediately becomes "43.6".  The data is pulled from a Sharepoint list which has the column settings for "Currency".

From what I have been able to research, the only way to accomplish formatting currency in this way is through a macro.  I've attempted to apply a macro in several places in the document, and have not had any success.  Any insight would be greatly appreciated.

[v-bacao-msft]

Hi @Jason_Collet ,

Have you seen the format of this field value in Flow run history?

We need to determine if the field has been formatted in Flow or changed when it is inserted into Word Template.

If it is the former, we may be able to make changes in Flow; if it is the latter, I am afraid that Flow is not working.

Best Regards,

[Jason_Collet]

Thank you for the prompt reply.  Just ran the flow again, and you are spot on...that is the culprit:

For good measure, here is the "Populate a Microsoft Word Template":

Is there an Expression I am supposed to apply against the Dynamic Content to keep the column settings as Currency?

[Jason_Collet]

From my research (please see the other posts in this thread), it is indeed the *former*--the field has been formatted in Flow.  What changes may be made in Flow to allow for currency format?

[bradleyhorton · Accepted solution]

@Jason_Collet  did you resolve this?

You might be able to use the formatnumber or float expressions?

[Jason_Collet]

My apologies, did not see the reply.  I most certainly *did* get this resolved.  My initial solution was a convoluted mess (it worked but man was it a spaghetti tangle) but once the FormatNumber came out, I was able to revise the flow to what I had hoped for.