My strings lose their formatting once they hit my feature merger. Any help would be greatly appreciated.
+6
Hi @sashalockamy,
May we ask for a bit more information please? What kind of formatting is lost in the string? Do you have a sample workspace or data you can share with us? Screenshots would also help, if you would prefer not to share data.
It would also be great if you could share some details about the build of FME you are using as there have been some updates to the FeatureMerger since 2016.1.
Any assistance or information you are able to provide that helps narrow down the issue would be fantastic.
Cheers,
Annabelle
+2
Please add some context to help everyone understand the problem to help you!
Give examples please.
+6
- Contributor
- 28 replies
-
23 January 2018
Sure. Below, at attributeManager_2 to inspection, my strings look great, but once they go through the FeatureMerger_3, the output reformats my strings...
+6
- Contributor
- 28 replies
-
23 January 2018
Sure. Below, at attributeManager_2 to inspection, my strings look great, but once they go through the FeatureMerger_3, the output reformats my strings...
here is the desired output at shown in inspection results desired-output-inspection.png
here is the actual output which is no good because it reformatted my string to 2240 vs 0224 in the usaa_acct field actual-output-no-good.png
+6
- Contributor
- 28 replies
-
23 January 2018
@mark_1spatial I added info on my issue... will you please take a look?
+6
- Contributor
- 28 replies
-
23 January 2018
I was able to create a secondary workspace to merge two outputs and get the results I needed. Still not sure why the feature merger was changing my string length...
Userlevel 2
+17
- Contributor
- 7539 replies
-
24 January 2018
Do you perhaps look at the resulting CSV table with Excel? Excel displays this CSV table like the screenshot below.
value
0019
019
19
0019-2240
019-2240
19-2240
Reply
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.