I tried to apply resource files with the "Invoke-PnPSiteTemplate" PowerShell cmdlet and it worked sucessfully.
I suggest to add a new file collection property to the "Provision PnP template to SharePoint" action where we can add resource files and they are uploaded to the same path where the template file is created:
We discussed the issue and a possible workaround is to place the XML file and the RESX files in one folder then build a PnP template using a PowerShell command Convert-PnPFolderToSiteTemplate. Check out the example here and then apply the PnP template in the Plumsail action.
So, you won't need to locate the resx file specifically since they will be included into the PnP template.
Thank you for the workaround, but, unfortunately, it doesn't work for me, since I'm building the template content on the fly with Power Automate.
I'm using different Power Automate actions to get the content from different data sources and compose the XML code that will feed the "Provision PnP template to SharePoint" Plumsail action.
Please note that the template content will be different on each run, because the data sources are constantly changing.
It would be great to have those additional parameters so that resource files —and localizations— can be used in one of your most useful actions.