Skip to main content
Question

Is there a way to populate parameters before opening a work space?

  • April 20, 2020
  • 2 replies
  • 47 views
afod
Contributor
Forum|alt.badge.img+6

I am having some issues with the 2020 install and i have had to move over to a different PC. I migrated everything fine, but when i open the workspaces, the first thing that occurs is the feature readers try and find the old database and then drop all the feature types that were previously being read.

 

Some of these have 10 or more specific features, all with multiple links so it will take a long time to try and re-link them in, is there any way i can change the parameter without opening it, then open it up?

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.

2 replies

takashi
Celebrity
  • takashiCelebrity
  • April 20, 2020

Hi @afod, I think it depends on how you configured the database connection in your workspace.

For example, if you have set a database connection name to the Dataset parameter in the FeatureReader, you can export the definition of the connection from the old PC and import it to the new PC before opening the workspace in the new PC. Then FME on the new PC can access the database with the same connection name as the old PC, and therefore the feature types configuration can also be kept.

To export/import a database connection, open the FME Options window (Workbench menu: Tools > FME Options), go to the Database Connections page, right-click on the connections list > Export/Import.

Why not inspect features with Visual/Data Preview and Feature/Record Information before writing them into a destination dataset?
afod
Contributor
Forum|alt.badge.img+6
  • afodContributor
  • Author
  • Contributor
  • April 20, 2020

Hmm i see, it was configured purely with just a created linked user parameter. Then just select the SQLite DB from explorer.

The weird thing is i have been able to send the workspace to clients who have to go in manually and re-path it all before they run it and this didn't happen to them (2019) FME.

If the work space is run via a runner without any interference it works fine but as soon as i open it all the readers drop back to just having a Generic port only.

Community Stats

32,545
Posts
123,579
Replies
40,792
Members
Terms & ConditionsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.