There is already a report for the problem (reference FMEENGINE-59779) and I will follow up with the developers and product managers to see if we can get this one fixed quickly, as there are a lot of users affected.
The workaround is to have each feature type (layer) listed separately in the workspace and not to use the Feature Type Merge Filter. It will take up more space in the workspace, but you can put a bookmark around it and collapse it, and that would help.
Apologies for the inconvenience, and thank you for your patience.
There is already a report for the problem (reference FMEENGINE-59779) and I will follow up with the developers and product managers to see if we can get this one fixed quickly, as there are a lot of users affected.
The workaround is to have each feature type (layer) listed separately in the workspace and not to use the Feature Type Merge Filter. It will take up more space in the workspace, but you can put a bookmark around it and collapse it, and that would help.
Apologies for the inconvenience, and thank you for your patience.
There is already a report for the problem (reference FMEENGINE-59779) and I will follow up with the developers and product managers to see if we can get this one fixed quickly, as there are a lot of users affected.
The workaround is to have each feature type (layer) listed separately in the workspace and not to use the Feature Type Merge Filter. It will take up more space in the workspace, but you can put a bookmark around it and collapse it, and that would help.
Apologies for the inconvenience, and thank you for your patience.
So I got in touch with the development team responsible for this. Ironically (if that's the word) I missed their weekly meeting this morning by a few minutes, so we'll have to wait until next week for them to look at the issue - but I'm told it is now a "priority fix" and we'll see some action on it shortly.
So I got in touch with the development team responsible for this. Ironically (if that's the word) I missed their weekly meeting this morning by a few minutes, so we'll have to wait until next week for them to look at the issue - but I'm told it is now a "priority fix" and we'll see some action on it shortly.
So I got in touch with the development team responsible for this. Ironically (if that's the word) I missed their weekly meeting this morning by a few minutes, so we'll have to wait until next week for them to look at the issue - but I'm told it is now a "priority fix" and we'll see some action on it shortly.
I tried your workaround and it works, but if we hava a lot of feature (Layer), it's take place even with bookmark :(
Do you need to specify the feature types/layers to read? If you don't specify, it appears to read layers even with accented characters with no issues.
It also doesn't appear to be a problem for the FeatureReader even if specifying feature types to read, so you could use that with the generic port
Yes. It's better because i have a lot of layer, but i can put a testfilter after reader where i don't specify the feature. I'm goint to test your idea and i let you know the result.
Yes. It's better because i have a lot of layer, but i can put a testfilter after reader where i don't specify the feature. I'm goint to test your idea and i let you know the result.
The FeatureReader option that I just edited my answer to include may be better in that case
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.
