Hi,
I'm using the FTPcaller to upload data on a weekly basis. In order to preserve data already posted, the new file has an changing date in the file name.
I've configured the Transfer > URL portion of the FTPCaller to accept an attribute value which works fine. However, when I try and do this with the Upload From A File > File To Upload portion, the FTPCaller fails, saying it cannot find the file:
Any idea what I am doing wrong?
Not sure as I did not test this, but maybe is is a simple as adding one or two extra backslashes in the fileLink attribute, as it is also an escape character and the log only shows one?
Hi Niels,
Sadly not as FME cannot still find the file even with the escapaed backslashes:
I have just fixed this using an AttributeManager rather than a AttributeCreator. I didn't have to escape the backslash so all good. Thanks for your help!
I have just fixed this using an AttributeManager rather than a AttributeCreator. I didn't have to escape the backslash so all good. Thanks for your help!
Nice! Thanks for the feedback.
Really puzzled. Can you please retest if this does not work with an AttributeCreator? Copy pasting the line from the manager to the creator? What version do you use?
Personally, I never use the AttributeManager (I can't stand the red cog when changing the attributestructure upstream...) so I wonder why this is happening.
Nice! Thanks for the feedback.
Really puzzled. Can you please retest if this does not work with an AttributeCreator? Copy pasting the line from the manager to the creator? What version do you use?
Personally, I never use the AttributeManager (I can't stand the red cog when changing the attributestructure upstream...) so I wonder why this is happening.
Ah so, the issue seems to be not the ButeManager / ButeCreator but the fact I was readiing in the filepaths from a csv I had created with Excel.
Using the FeatureReader to pull these out, and then using the AttributeCreator to create the entire file path results in the FTPCaller not finding the file:
Odd!
Nice! Thanks for the feedback.
Really puzzled. Can you please retest if this does not work with an AttributeCreator? Copy pasting the line from the manager to the creator? What version do you use?
Personally, I never use the AttributeManager (I can't stand the red cog when changing the attributestructure upstream...) so I wonder why this is happening.
Happy to hear the issue was not solved by the AttributeManager :S :D
I think you should check if your CSV reader does interpretation of the field types, I think this is the case as it is default. This might result in an incorrect attribute type for what you want. You can set it manually to string.
Nice! Thanks for the feedback.
Really puzzled. Can you please retest if this does not work with an AttributeCreator? Copy pasting the line from the manager to the creator? What version do you use?
Personally, I never use the AttributeManager (I can't stand the red cog when changing the attributestructure upstream...) so I wonder why this is happening.
Nice! Thanks for the feedback.
Really puzzled. Can you please retest if this does not work with an AttributeCreator? Copy pasting the line from the manager to the creator? What version do you use?
Personally, I never use the AttributeManager (I can't stand the red cog when changing the attributestructure upstream...) so I wonder why this is happening.
This part.
Nice! Thanks for the feedback.
Really puzzled. Can you please retest if this does not work with an AttributeCreator? Copy pasting the line from the manager to the creator? What version do you use?
Personally, I never use the AttributeManager (I can't stand the red cog when changing the attributestructure upstream...) so I wonder why this is happening.
Hi Niels,
Thank you - I did alter that part and am now testing.