Creating a top-level folder in Resources via fmeflowconfig.txt causes the folder to appear in the UI, but does not create a macro. This means $(FME_SHAREDRESOURCE_MOI) will not be recognised by Flow when the workspace is run (assuming this is the SHAREDRESOURCE_NAME value you set, from @frro’s answer).
To mimic the expected behaviour from macros referencing top-level Resources, you can create a Deployment Parameter with name FME_SHAREDRESOURCE_MOI and value “C:\ProgramData\Safe Software\FMEFlow\resources\moi” or wherever the new moi folder is located. This allows $(FME_SHAREDRESOURCE_MOI) to be recognized in User Parameters or within Workspaces.
Please let me know if you have any questions about this!
Creating a top-level folder in Resources via fmeflowconfig.txt causes the folder to appear in the UI, but does not create a macro. This means $(FME_SHAREDRESOURCE_MOI) will not be recognised by Flow when the workspace is run (assuming this is the SHAREDRESOURCE_NAME value you set, from @frro’s answer).
To mimic the expected behaviour from macros referencing top-level Resources, you can create a Deployment Parameter with name FME_SHAREDRESOURCE_MOI and value “C:\ProgramData\Safe Software\FMEFlow\resources\moi” or wherever the new moi folder is located. This allows $(FME_SHAREDRESOURCE_MOI) to be recognized in User Parameters or within Workspaces.
Please let me know if you have any questions about this!