Problem with import table in dataservices

[former_member824462]

This isn't the first time we've been having problems transporting jobs with camel case tables.

When I export an job atl file from a test environment to a production environment we see strange effects.

the tables present in the job are shown in this

way only post REIMPORT ALL from the datastore the situation seems to normalize

but not for all, for example see this table used and shown with usage = 0 (before the reimport it was the only one together with another one to have USAGE=1)

What is going on?

I anticipate that we have also already used the workaround of inserting the case sensitive = Yes inside the ATL FILE but in the reimport of the datastore many errors were created in the existing jobs.

We urgently need to understand how to safely carry out these transports

Thank you

[Nawfal]

Hi Martino,

When you import a table in your datastore, do you use double quote marks in between the name to preserve the name casing? If yes may be worth trying to import a table by name without any quotes and see how BODS interprets the name. Else if you don't use quotes on import then try it with and test in each case the export/import of ATL to see which one way is causing the problem. It seems that some symbols in the name are the cause of the issue.

Thanks

Nawfal

[former_member824462]

Hi Nawfal,

if i try to import table without tring quotes i get an error that the table doesn't found.
I also repeat the import with string quotes but the result doesn't change.
Before the reimport all this table was the unique that have 1 USAGE and other = 0 as i said previous