Bug with Unique ID widget when use in Power Automate

Hello

I am using your "Submission ID" with Power Automate, and the "Submission Id" number is too long for our needs, so I decided to switch over to your "Unique ID" widget.

All was working fine with the "Submission Id" and the addition of the following widgets, to create a project folder in SharePoint.

"DateTime Single" - "Submission ID" - "Short Text"

This would produce a project folder in SharePoint as follows:

2020-06-16 - 4681480250421187768 - CANADA

The "Unique Id" widget that we want to switch over to, is causing an error in Power Automate, as it is inserting a carriage return after the data.

How can we fix this?

We apologize for inconvenience. I have been testing also using the unique ID widget as folder path to determine if there is carriage return included in the data. 

But so far in my test (using dropbox folder), I could not reproduce the same issue yet.

In your screenshot image, I noted that there is another "short text" included as suffix the the full folder path name. Can you tell us how did you append the "short text" after the Unique ID widget for the folder path?

I could not recreate the appending of additional texts(after Unique ID) within the Form Builder.

Let us know if issue persist. We will wait for your updated response.

Since I could not get your Unique Id widget to work because of the carriage return issue, I have opted to use the Salesforce Name. And I did have it setup as you have shown above. We used FSR- instead of Jot-.

But, to answer your question, in the image, where you see the blue Salesforce Name item, which we are calling, "Service Request #", this is where I was putting your Unique ID item. It was not working with your Unique ID. But it is working with our Salesforce Service Request #. Hence, I achieve the same thing, and now my file name actually has the same number that is found in Salesforce.

I do recommend that you look into your Unique Id widget, as it is adding a carriage return when trying to integrate in Power Automate.

Case closed on my end.

Thank you

Thank you for taking the time updating us on the status and letting us know you were able to come to a resolution.

I will also do further investigation and test it with Power Automate once I get copy of it. I will submit report to the development team also once I identified the issue.

Feel free to contact us anytime should you need assistance again.

Best