Solved: Inputting Datafields from Powerapps for Power auto...

Anonymous · ‎04-19-2020

Hi everyone,

My flow is running smoothly. The only issue I have having is when inputting the fields that I want filled in within my Word doc from powerapps, it's requiring me to input fields that are within my flow that are now data-fields within my powerapps such as (Createfile_FileName). These are not data fields. What should I put within these mandatory fields? Attached are the fields that are questionable. Highlighted in yellow within the grey box at the top. Attached is my flow also. Thank you!

WarrenBelz · ‎04-20-2020

@Anonymous ,

This is precisely what I have been trying to convey to you in so many different ways. You need to send a unique file name to the flow so it does not overwrite existing documents - which is exactly what it is doing now. You have three places in the Flow (as I said it could have been one if you re-used the parameter), but the name needs to be something that will not be repeated - do not follow your friends and put "". I gave you some code almost at the start to do this

Set(
   vFileName,
   DataCardValue50.Text & "_" &
   Text(
      Now(),
      "[$-en-US]yymmdd_hhmmss"
   )
);

If you put this in the code before the Flow run code, you just need to put vFileName in those three places in the PowerApps Flow parameters.

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

View solution in original post

WarrenBelz · ‎04-20-2020

@Anonymous

Yes - I was missing a comma - free-typed it (now fixed in post so as to not confuse people reading it). Your code is below

Set(
   vFileName,
   DataCardValue50.Text & "_" & 
   Text(Now(),"[$-en-US]yymmdd_hhmmss")
);
AutoFillSS.Run(
   DataCardValue14.Text,...Text,DataCardValue49.Text, 
   vFileName,vFileName,DataCardValue67.Text,vFileName, ...DataCardValue62.Text
)

Seriously, for your own sake for going forward with Power Apps, take some time to understand the code you are implementing - always keep this reference guide in your favorites and each time you get a new command, look it up and match what you are doing with the suggested usage, otherwise you will spend hours trying to fix code.

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

View solution in original post

WarrenBelz · ‎04-19-2020

Hi @Anonymous ,

The one you are referring to is the name of the file that will be both your Word (.docx) and PDF (.pdf) file.

You simply need to tell the Flow what to call it. You generally need to give it a unique name if you are filing multiple in the same location (otherwise the new one will overwrite the old one).

I generally use identifiers from the list and append the date and time in ddmmyy_hhmmss on the end so the name has to be unique - it looks something like this

YoutIdentifierControl1.Text & "_" &
YourIdentifierControl2.Text.Text & "_" & 
Text(
   Now(),
   "[$-en-US]yymmdd_hhmmss"
)

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

Anonymous · ‎04-19-2020

@WarrenBelz Yes i'm referring to those.

How do I give it a unique name? I name it within flow or within powerapps and how?

The identifiers are coming what from list and how do you pick them?

Where do you input this code? Sorry just trying to understand.

WarrenBelz · ‎04-19-2020

Hi @Anonymous ,

I am simply saying you need to name the file - the Flow is asking for this and you are not providing it.

You can call it "Test" if you want to, but it will be overwritten every time.

I tend to set a Variable to this value in the code immediately before the Flow and then send the Variable to the Flow - so

Set(
   vFileName
   YourIdentifierControl1.Text & "_" &
   Text(
      Now(),
      "[$-en-US]yymmdd_hhmmss"
   )
)

You can choose whatever you want as the identifier - the only reason it needs to be unique is so it will not be overwritten by the next file. To answer where you would put it - exactly where you have your cursor in the ''" in your screenshot as the Flow is expecting some text to name the file you are producing. In the case of using a Variable as above, you would put vFileName (no quotes) in there.

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

Anonymous · ‎04-19-2020

@WarrenBelz

I am still confused. Let me what I'm not understanding correctly please because currently my flow isn't working due to "Run" having invalid arguments. Attached is my new flow and let me know how to name the file. I tried to copy a tutorial. Let me know if I should set my flow up differently.

I have a file within Sharepoint where I'm directing the word and pdf files named (Form Submissions). Do I add this file name somewhere within powerapps? Attached a copy of the word template " VHO Standard Submissions..." within Convert Word doc to PDF. Not sure if that's correct.

When you say name the file, I'm guessing you mean within the flow. Where "Create File" > "File Name" is, do you want me to put a name before the pink box, for example as "Test?" If not, where do I put "Test?" And where exactly do you put this code within your flow?

Where do I put this code? I really don't know much, please be specific. The VFileName is my case would be "Form Submissions"

Please list step by step what I have to do to complete this. Sorry for the confusion.

WarrenBelz · ‎04-19-2020

@Anonymous ,

Firstly help by telling me if you wrote this Flow from knowledge or simply followed a video as what you keep asking is the most basic of Flow parameter elements.

A Flow has parameters which you set by putting Ask in PowerApps in the relevant field in the Flow. When you run the Flow, you have FlowName.Run(Parameter1, Parameter2, Parameter3 . . . . .) until the end. You can see the names and order of these in the top panel and in one of your screen shots you have the cursor exactly where you need to put the file name (as this is the order you must have entered the Ask in Power Apps in the field when building the Flow).

All you are missing in the Flow parameters from what I see is the file name, which is always different from the template (otherwise it would overwrite the template and you could not do another Word merge). If you do not want to save these files (for instance if you email them) then you call the file whatever you want (my test example), but I suspect you may want to keep them in Form Submissions, hence the specs for unique file names.

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

Anonymous · ‎04-20-2020

@WarrenBelzYes, I followed a video but was an Onedrive merge instead of a Sharepoint. I don't know much about flows. I did use "ask in powerapps" for parameters.

And yes, I do not want to overwrite the template and I do want to keep them within the file "Form Submission."

I am missing Createfile_FileName, Createfile_FileName_1, and ConvertWordDocumenttoPDF_file

Anonymous · ‎04-20-2020

@WarrenBelz

Update: Flow works fine through power automate and form is stored within Sharepoint.

Through powerapps the code doesn't work as the Run function has invalid arguments.

For Creatfile_FileName I put the datacard# for ID that my friends told me to do and he said to put "" for the rest. Not sure if this works

Attached is my updated flow

WarrenBelz · ‎04-20-2020

Hi @Anonymous ,

I am not sure how much your friends know about Flows, but from the very start of this, I have been simply asking you to name your file and put the result where the Flow is asking for it. This is where you had your cursor in your screen shot which was Createfile_FileName

Also Createfile_FileName_1, needs the same name (definitely not "" as this would result in an unnamed PDF)

ConvertWordDocumenttoPDF_file (although you have not shown this in your Flow) will also probably require a value.

You can actually re-use a value in Flow by simply pasting a value already requested into the area instead of using "Ask in Power Apps" - you could have done this in the PDF name and only needed to send one value to the Flow.

Putting your ID will work if you only do one document for the ID, otherwise it will be overwritten by the next document filed, which is why it is good to put something describing the document in the name - you can do this from a value on your screen or in the data source of the item.

Can you please tell me if you understand what I am conveying here as I am running out of different ways of describing it.

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

Anonymous · ‎04-20-2020

@WarrenBelz

I think I'm understanding you. You want me to put the names within Powerapps where the grey box is indicating not within the flow in Power automate.

I put the ID datacard and time stamp DataCardValue50.Text&Now() for Createfile_FileName, Createfile_FileName_1, and ConvertWordDocumenttoPDF_file.

I do only want one ID per document submission. So as the form gets submitted I want an ID number and time stamp with the word doc and PDF. Another new form will generate another ID. Although, how can I put a descriptive name? Please clarify "you can do this from a value on your screen or in the data source of the item." Do I put "Testname" before DataCardValue50.Text&Now()

or within the flow in power automate somewhere? I don't want my submitted documents (forms) from being overwritten.