0
Planned
Validate CSV File exists on connector creation
If you add a CSV connector, and in the file path you put a CSV that doesn't exist, the workflow is a bit unfriendly.
It creates the connector (which isn't obvious), but redirects you to the homepage with the following screen:
This seems to happen because it tries to load the CSV file to get the schema but can't.
I feel like it would be better to validate the file exists when creating the connector. If it doesn't, either throw an error that stops creation - or still show the connector page but show a schema error further down.
On another funny note, if you navigate to the connector page after creation, this is what displays:
It has trouble loading the connector image URL - it puts something really really funny into the image link:
This seems to happen because it tries to load the CSV file to get the schema but can't.
I feel like it would be better to validate the file exists when creating the connector. If it doesn't, either throw an error that stops creation - or still show the connector page but show a schema error further down.
On another funny note, if you navigate to the connector page after creation, this is what displays:
It has trouble loading the connector image URL - it puts something really really funny into the image link:
<img alt="Unify.Connectors.CSV - The CSV connector allows for manipulation of a source CSV file. Useful for solution testing." class="AutoThumbnail" src="1b175bc1-da20-4064-9d74-d43e5744931f.connector" style="vertical-align: middle;" title="Unify.Connectors.CSV - The CSV connector allows for manipulation of a source CSV file. Useful for solution testing.">
Only fixes when you go into "edit connector" and "save". Saves successfully and shows the correct image after (even if the csv file still doesn't exist).
Customer support service by UserEcho
Planned for 6.0 release