nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

IWDatacapture.save() method

iw_store

Hi ALL,

Server : Teamsite 6.7.2 on Windows 2003 SP2.

I have a DCT and on IWEventRegistry.addFormHandler("OnGenerate",handleGenerate), I call a CGI asking name for DCT. When user provides name in CGI using that name I save the DCT inside data folder using

IWDCRInfo.setDCRName(savePath);
IWDatacapture.save();

Then I edit the same DCR and make few changes and again I click generate, but this time I don't ask for name, I just save with old name using IWDatacapture.save() method.

While doing so I am getting an alert with message "[color=red]The file you are trying to save is being modified by different user. Do you want to overwrite the file?" with two buttons at the bottom Overrite or cancel. [/color]

This was not the case with Teamsite 6.5, but I am getting this message only in 6.7.2. Same user is doing all above steps.

When I look at document IWDatacapture.save(); is a kind of forced save. No idea what has changed in 6.7.2.

Could any one help me, how can I avoid that alert ? any pointers ? I just need forced save.

Thanks,

Sanjeev

Find more posts tagged with

Comments

ISCBorisB

IWDCRInfo.setDCRName is an asynchronous call that spawns dedicated Server thread. So, in the following code "save"
starts immediately after "setDCRName" call, well before Set Name process is done and probably before Server thread
started. That introduces racing and you can not tell upfront which thread wins.

IWDCRInfo.setDCRName(savePath);
IWDatacapture.save();

I'm not sure if that's what causing you problem, it may well be. If "save" thread wins the race, "loser" setDCRName thread
*may* leave File Owner as IWAM_xxxx / TSIMP_xxxx, etc. I've illustrated one of the possible re-synchronization Methods [post=98599]here[/post],
take a look. Note that you would not need all of it, just check pending / Timeout.

iw_store

Hi,

Thank you. I am getting that message (or error) when I frire IWDatacapture.save() on a dcr which has a name already with it, without firing IWDCRInfo.setDCRName(savePath);.

I fire below sequence only when DCR is new, I mean when DCR has no name
IWDCRInfo.setDCRName(savePath);
IWDatacapture.save();

Above code runned for years in 650 sp3.

Looks like this is a bug with 672.

I have a normal datacapture.cfg, no JS. I fill in data and save it, and close the form. I edit the just saved DCR and change little bit and say save. I click again save

Immediately

, I get save error with message "The file you are trying to save is being modified by different user. Do you want to overwrite the file?"

ISCBorisB

Looks like this is a bug with 672.

I have a normal datacapture.cfg, no JS. I fill in data and save it, and close the form. I edit the just saved DCR and change little bit and say save. I click again save
Immediately
, I get save error with message "The file you are trying to save is being modified by different user. Do you want to overwrite the file?"

You did not mention before that you have the same issue without FormAPI. If that's the case it has nothing
whatever to do to IWDatacapture.save (or any other) method.

Have you contacted support? Does the problem manifest itself for any user and any DCT Type? It's extremely
hard to believe that it's IWOV bug. 6.7.2 has been out for quite a while now, such rough problem would have
been known and reported months ago

iw_store

You did not mention before that you have the same issue without FormAPI. If that's the case it has nothing
whatever to do to IWDatacapture.save (or any other) method.

Have you contacted support? Does the problem manifest itself for any user and any DCT Type? It's extremely
hard to believe that it's IWOV bug. 6.7.2 has been out for quite a while now, such rough problem would have
been known and reported months ago

When I started investigating problem in my code, then I came to know it's happening without FormAPI.

I have asked our infra team to raise a support case.

Will post the outcome of post here.

Thank you for the Help!

iw_store

IW has confirmed us that its a bug with TS 672, will fix it in next service pack.

Frederik

FYI...

we've seen this also, I think... We've had similar stuff on LiveSite pages and DCRs, and I've reported about it on LS sub-forum:"Locking Issue in SitePublisher"

ccprofessional

Here's my story:

This bug (and it is a bug) was first noticed when we upgraded from TS 6.7.1 to TS 6.7.2 SP1. IW Support confirmed the bug and mentioned that would be fixed in SP2. We upgraded from TS 6.7.2 SP1 to SP2, and still face the issue. IW Support tells us that this issue occurs only if we upgrade from SP1 to SP2, but would not occur if SP2 was applied from TS 6.7.2 base.

So annoying!

To recreate the bug, just take any out of box DCT, with no formAPI and save a DCR. Regardless of the time you wait between saves, you get the following message upon the *second* save (subsequent saves are fine).

The file you are trying to save is being modified by different user. Do you want to overwrite the file?

I obviously do not want to uninstall SP1 and reapply SP2 and pray that it is fixed.

I'm willing to try some FormAPI workarounds - perhaps something (crazy) that overrides the onSave event the second time.. Chime in with your ideas.