Assuming it’s possible, FME Form should look in the same folder as the workspace for FME related components - e.g., CustomFormats, CustomTransfomers.
In FME Flow if you have a CustomTransformer which lives in the same repository as a workspace it will work. It would nice to be able to keep CustomTransfomers in the same location. As it is right now in FME Form if you want to keep all files related to a porject together you need to copy the version from the location where FME can find it (e.g., FME folder) to your project folder.
The process is problematic because you quickly run into issues with copying and keeping track of the version which you’re actually working with in workbench vs what is in your project folder.
Open
Look in workspace folder for FME components (e.g., CustomTransfomers)
+48- Celebrity
+9- Safer
Hi
+48- Celebrity
Hi
Any progress on this?
I’ve really been struggling and over engineering things to try and work around this.
A way to be able to embed a CustomTransfomer via command line would be so so helpful (e.g., some kind of “Compile” argument in workbench.
Working with git it’s super annoying to have a large workspace, especially if you want to have multiple branches. Solution: Linked CustomTransfomers.
Only they area a REAL pain to work with. The problems I’m having to work around:
- They always have to be in the FME folder. If they are not in there and up-to-date then it all falls apart. If I want to keep the CT in git then I need to also have a process/script to export to the FME Folder for general use. If this folder is a shared location on the network for example then you don’t want to overwrite something that is being used in other projects.
- The work around it to have a custom launch script to first pointing to the project folder.
- Editing them in context has to be done when they are embedded. Then the transformer needs to be Re-Exported and you need to overwrite the old one. Versioning is lost (but that’s somehow acceptable because of GIT).
- Dependency Hell: If a linked transformer is missing or out of date the house of cards collapses.
- Work around is an extremely hacky script to manually embed the content of the CustomTransformer directly into the workspace file. This is extremely limited and not a good idea at all.
I think the same could be true for a PythonCaller and SQLCallers. Where the content of a PythonCaller is external to the workspace and can be edited separately from the workspace. All of this is to reduce the amount of conflicts which come about when working with FME in GIT.
It’s honestly been a real turn off for me over the last few years wanting to work more in git. I’ve found myself moving more and more away from FME and into the pure code (It’s especially true now that we have Agents).