DSXchange

Hi All,

I have encountered a wierd issue during an import/export.

We had to refresh the QA code with that in production. We took the export from Production.
We modified the .dsx with the read only '1' to '0' to make it writeable.
But after doing that .dsx size changed to 0KB (i.e it was empty).

Anybody has any idea what could be the reason for this?

Bad edit?

Can you reproduce the problem?

SandhyaShetty21 wrote:But after doing that .dsx size changed to 0KB (i.e it was empty).

If you edit a file and it's empty afterwards, I'm going to have to side with Andy.

Thanks All for your prompt replies.

What we did was, Since it was a huge export, we replaced all the read-only from '1' to '0'.

Do you think this is an incorrect way to make a job writeable.
Is there any other way?

As a workaround we just imported it without changing the read-only from 1 to 0. But not quite sure if may have problems. So can you please let me know if its really required to change read only from 1 to 0 before importing.

You have to change both job level attributes and stage level attributes.

Of course, modifying the dsx is not supported, and you do so at your own risk, but for more details, check out the description of the "manual" method in this post:
viewtopic.php?t=130036

Agreed modifying the dsx is not a recommended approach to make the dsx writeable. But i am unaware of any other approach.

Can you please suggest what needs to be done to make the dsx writeable.
If I am directly importing the code without making any changes to read-only parameter what problems can i expect.

SandhyaShetty21 wrote:If I am directly importing the code without making any changes to read-only parameter what problems can i expect.

I don't think that will give you a problem but all you can do is, view or run the job. You will not be able to edit it.

If the size of the DSX file is now 0 bytes you have managed to empty it of content, probably by using the wrong command in whatever editor you're using.

Welcome to last week, Ray.

ray.wurlod wrote:If the size of the DSX file is now 0 bytes you have managed to empty it of content, probably by using the wrong command in whatever editor you're using.

We have just replaced the read only = 1 field wherever present to read only = 0.

Hi,
I was wondering, was the read only attribute the product of importing to a protected project?
Might be worth while to protect and unprotect (via Administrator client) turn your jobs to editable?
(just thinking, cause I don't have DS V7 available)

P.S.
If you want to be able to edit your jobs you want the read only attribute set to 0

IHTH (I Hope This Helps),

Thanks all for your responses. However, I have been able to narrow down the issue to the Editor I used .. That was NOTEPAD++. Using Wordpad/Notepad for replacing the ReadOnly field works perfectly fine.