Skip to main content

For example, projectname: X has a MethodType:Vegetation. When one chooses Project name X, MethodType:vegetation should autopopulate. This ensures correct method type gets picked up without spending time to identify the methodtype for that projectname especially if there are many methodtypes.

Like this? I created an attribute called projectname and filled it with user attribute $(ProjectName). When running the workspace, the user can enter X and the TestFilter transformer guides the features to the correct StringConcatenator, where the MethodType field is populated with the string 'Vegetation'.

imageIf you generate projectname values somewhere else in your workspace, you can still use this workflow:

image


Reply