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!
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
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!