PAD Import using notepad issue

[Luzviet]

So i have this notepad consisting of pad code that translated into notepad form , my senior said to me just copy the notepad into pad in subflow but when i do it. this error message appears like on the picture

any help?

i already tried to delete the local data of power automate desktop and it wont solve the problem

[WillSG]

Hi @Luzviet  I hope you are doing well.

If possible, please share the notepad with the snipped code, so someone here can help you out with this issue, that would be easier.

Happy automation!,

If I have addressed your inquiry successfully, kindly consider marking my response as the preferred solution. If you found my assistance helpful, a 'Thumbs Up' would be greatly appreciated.

Additionally, I offer specialized consultancy and development services leveraging PAD. If you're interested in exploring these services further, feel free to DM me, and we can initiate a discussion.

Finally, here is my LinkedIn Profile so you can connect with me.

Kind regards,

Will SG

Managing Director & Automation Lead

RAMS CR (Recruitment & Automation)

[eetuRobo]

Are the PAD versions the same? You might have different versions of PAD and thats why you cant paste the code since some of the syntax of the actions have changed.
So ask what version your senior has and check if you have the same. If not ask your senior to update their version of PAD and you do the same so you both have the same version and ask them to send new notepad file of the code.

If for whatever reason you can't have the same version then try pasting the code in little bits.
Try adding couple of lines of the code to your empty flow. If it gives error take some lines from the middle and see if that works.
If its not too long flow then line by line or in multiple lines. There might only be one or two actions that don't match in your version. Then you can add those couple actions manually.

[Deenuji]

Kindly ensure that both of you are using the same version of PAD.

Furthermore, I observed that you activated Power Fx while crafting your PAD flow. Please attempt to generate a new flow by deactivating Power Fx, as indicated below.

Then, paste your notepad code and verify if it resolves your issue.

Thanks,

Deenu

[Agnius]

PAD is backwards compatible, but only backwards. So, if your senior is using an older version of PAD than yours, you should be fine. But if they're using a later version than yours, that may be causing the issue. The only way to work around that would be for you to upgrade to the same (or later) version that your senior is using.

Also, as mentioned by @Deenuji , you should also check with your senior on whether they also had Power Fx enabled on their flow. If they hadn't, you shouldn't enable it when you're creating your flow either.

Finally, if they are using any Premium actions and you don't have a Premium license, you won't be able to use the code.

[Luzviet]

hello guys thank you for the suggestion im still asking the senior, but based on what i get from you guys. i already did copy some of the notepad and from 8 only 1 is succesfully copied without this issue happening

[Deenuji]

@Luzviet 

Could you kindly confirm whether you disabled the Power Fx option while creating your new flow in your PAD, as mentioned earlier?

Still there might be chance of version incompatibility. So please check with you colleague and align on the same.

Warm Regards,

Deenu

[Agnius]

Versions may still affect that. If in that 1 flow that was successfully copied, no actions with syntax having changed were used, you would be able to copy it, but others would fail. So, this does not rule out the versions issue, but it likely rules out Power Fx incompatibility.

Also, it still does not rule out the possibility of Premium actions being used. Again, if they were not used in the one flow that succeeded, you would be allowed to import it. But if premium actions are used in other flows, you would still not be able to import them.

[Luzviet]

i did that and nothing happen

[Deenuji]

@Luzviet 

The ultimate suggestion would be to verify the PAD versions with your senior and adjust your current version accordingly, either by updating or downgrading, and then attempt to paste the code again.

If the issue persists despite these adjustments, as mentioned by @Agnius , there might be an issue with premium actions being utilized in that flow.

If there are no premium connectors being used in the existing flow, and if you are using the latest version 2.41 or any higher, kindly consider downgrading to version 2.39 as many folks reporting different issues in current latest version.

Thanks,

Deenu

[Luzviet]

hello i have checked with my senior we are using the same version and no premium feature used

[Deenuji]

@Luzviet Which version of PAD are you both using?

[Luzviet]

2.41.170.24032 is the version that i used while he is using 2.29.127.23042

[Deenuji]

@Luzviet @Then it might be issue with PAD version 2.41 as many folks reporting different issues in this version. So I suggest you to downgrade your PAD version 2.29(same version what your senior having in his machine) or you also use 2.39. 

Another scenario involves changes in specific packages, such as Outlook. For instance, the features present in version 2.29 might differ from those in version 2.41, as Microsoft consistently introduces additional functionalities across all packages and actions. 

Thanks,

Deenu

[Chetan_Ninghot]

Hi,

In addition I want to said that , you can copy and paste data from text file to :- higher version to lower version or 

lower version to higher version of power automate desktop , its not having of version of PAD.

Its may be issue of specific 2.41 PAD version .......

(Note:- if you got your solution you can mark as solution and gives kudos)

Thanks & Regards

Chetan Ninghot

[Agnius]

This is not true. You can paste the code from a previous version to a later version, but not vice versa. If you try pasting code made with a later version to a previous version, you will usually not get anything (it will simply not be pasted at all). The only exception to this are cases when you are only pasting some basic actions that have not changed via the updates. But updates do break compatibility with older versions.