Welcome Guest! To enable all features please Login or Register.
Options
Go to last post Go to first unread
Dunners73  
#1 Posted : Wednesday, October 14, 2015 5:28:29 AM(UTC)
Dunners73

Rank: Member

Groups: Registered
Joined: 8/28/2015(UTC)
Posts: 10
United Kingdom
Location: London

Thanks: 1 times
I have noticed, that when you have a CSV connector, that has a wild card in the specified file name, you get an error when you try to write into the connector as a target.

Like this :

C:/DataFiles/OutputData*.csv

removing the wildcard fixes the error on write, but stops it being used for reading.
we have wildcards as our files have date time stamps in the name.

Due to this, we have doubled up on CSV connectors, one for output, one for input.

Is this a known issue / feature / bug ?

Thanks

Russell / Non Profit / IT Dept / UK Based
ipadmin  
#2 Posted : Wednesday, October 14, 2015 11:10:08 AM(UTC)
ipadmin

Rank: Administration

Groups: Administrators
Joined: 8/17/2015(UTC)
Posts: 22

Was thanked: 2 time(s) in 2 post(s)
Hi Russell

Not an issue that has come up before, but it is not really a bug. Specifying a wild card in the file name when that file is being created is not something that could be supported - Inaport would not know what to name the file.

Note that in the setup of the CSV connector, there is an option at the bottom under 'Target file processing options' to add a timestamp to the name of the file, thus allowing a single connector to create a new file each time the job is run.

For example, you you specified 'myfile.csv', the resulting file would be 'myfile_2015-10-14T12-08-10.csv'

Does that answer your question?
Dunners73  
#3 Posted : Thursday, October 15, 2015 4:07:03 AM(UTC)
Dunners73

Rank: Member

Groups: Registered
Joined: 8/28/2015(UTC)
Posts: 10
United Kingdom
Location: London

Thanks: 1 times
Thanks for the quick reply,

alright - i follow what you are saying, about wild cards having no logical meaning when creating a file - what im thinking that it would make it sense if inaport understood that & ignored (trimmed out) the wildcards before creating / writing to such files, while only using them in import/read operations.

re the datetime stamp, we are using that option datestamp option already & require it for archival purposes. works great.

The reason we have to read the date stamped files back in after generation, is so that we can mark off the records in CRM as exported following the export run. (Id rather update during export, but so far dont have a method for this with crm as the source.)

If there were an update to allow the system to ignore wildcards on creation, it would halve the number of connectors to maintain. (dev & live connectors too). perhaps by specifying 2 file paths, an import path (with optional wildcards) and an export path. basic solution, but that would do it.

Russell / Non Profit / IT Dept / UK Based
Users browsing this topic
Guest
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

Powered by YAF | YAF © 2003-2018, Yet Another Forum.NET
This page was generated in 0.136 seconds.

Notification

Icon
Error