This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
I have a workflow that opens a locally stored .mdb file, evaluates the contents then, if necessary, it rewrites the table with updated values. When it it is time to save this workflow to our private gallery, I ensure that the workflow dependencies are set to absolute. Then during the save process, I deselect the database asset to prevent from being encapsulated with the workflow.
But, it gets encapsulated anyway. I have other workflows that are set up in a similar way that this does not happen with.
Any ideas out there on how to prevent this from happening?
Thank you for your reply. To answer your question: The Input Tool path changes from the absolute path of the .mbd, to path to an "_external\a\1\" path.
I believe I've got this solved: One of my colleagues showed me that we can manage assets in the Configuration pane for individual tools/macros. There is a macro within my workflow that calls the .mbd, for some reason the macro was trying to encapsulate the .mbd even though I didn't want to encapsulate the macro!