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; } } }

Probelm with naming DCR

garima

I am using autonaming to name the DCR.
Based on the value in the dropdown the dcr is named.
i.e if dropdown-selection is abc then dcr is named abc.
I also need to check whether a dcr with abc name is already there or not.
For this I am using a call server.
But since the callserver is a separate thread, the dcr is getting saved before the call server returns.
Any workaround or pointers on how this can be resolved.

Find more posts tagged with

Comments

kaalraa

I am using autonaming to name the DCR.
Based on the value in the dropdown the dcr is named.
i.e if dropdown-selection is abc then dcr is named abc.
I also need to check whether a dcr with abc name is already there or not.
For this I am using a call server.
But since the callserver is a separate thread, the dcr is getting saved before the call server returns.
Any workaround or pointers on how this can be resolved.

Garima,

What event you are using to initiate the callServer... onSave or onSaveValid?? If you are using the former... then i suggest you to use the latter one... as it just validates your inputs on the form and call the script to check the existency for the name.

GroupingOnAggregation2.rptdesign

garima

I was calling the callserver in setAutoDCRPathgenerator's naming function.
SetautoDCrpathGenaerator was registered in init function.
But this approach is not working at all.

kaalraa

Thats what the reason might be as i am not sure but logically speaking this function must be called after Save only.

As i have earlier stated ... call the CallServer onSaveValid... which validates your values within the DCR and then calls the script to check the existence of name.

If it returns true... it will proceed with your onSaveDone and other registered events else on false provide an alert.

I hope it makes sense to you.

I was calling the callserver in setAutoDCRPathgenerator's naming function.
SetautoDCrpathGenaerator was registered in init function.
But this approach is not working at all.

chetansethi

Doing it on init would not work because init is called when the DCR loads. Whereas you need to check whether a DCR with same name exists or not after the user has selected the value in the DCR and has clicked on save.

To achieve this as Achin said you need to put the name check in the onSaveValid event.

I was calling the callserver in setAutoDCRPathgenerator's naming function.
SetautoDCrpathGenaerator was registered in init function.
But this approach is not working at all.

ISCBorisB

Thats what the reason might be as i am not sure but logically speaking this function must be called after Save only.

As i have earlier stated ... call the CallServer onSaveValid... which validates your values within the DCR and then calls the script to check the existence of name.

If it returns true... it will proceed with your onSaveDone and other registered events else on false provide an alert.

I hope it makes sense to you.

First, callServer method itself does not return anything.
Second, you can call it from onSave, onSaveValid or anywhere else before onSaveDone, as long as your handler returns true/false the way you want it.
Third, since the callServer method is asynchronous your code continues executing immediately after the call to callServer().

So, to do what you want you have to code basically three things:

See FormAPI guide for details

kaalraa

First, callServer method itself does not return anything.

CallServer provide output as a client script.. which in turn returns true or false.

Second, you can call it from onSave, onSaveValid or anywhere else before onSaveDone, as long as your handler returns true/false the way you want it.

Thats what i have said... call it from anywhere... but as the user needs to check the existence of the filename ... it must be before save or savedone.

Third, since the callServer method is asynchronous your code continues executing immediately after the call to callServer().

Thats true but still you can play around with the three parts of inbuilt Save functionality i.e. onSaveValid, onSaveNameSpecified and onSaveDone.

ISCBorisB

CallServer provide output as a client script.. which in turn returns true or false.

IWDatacapture.callServer method does not provide output of any sort, it (asynchronously) calls your Server Side script. Method does not return anything. Here is method Signature: IWDatacapture.callServer (url, data, isGet)
callServer method is not a Client Script
Server Side script you call being your own code can off course *return* true/false or anything else for that matter. Btw, return where? stdout, log File, somewhere else? Either way, your Client Side Form won't know that. Matter of fact, unless your (Server Side) code calls back to Client Side Form it won't even know that execution has been completed

deepakb

Yes, what ISCBorisB says is right.

Callserver is asynchronous call, and hence the calling program in this case DCT will not know whether the callserver has been successful or not. The onus is on the called program write some value back to DCT.

Here is how I had done in one the implementation.

1) In OnSaveValid make a call to this callserver, and return false from this OnSaveValid function. This stops the DCR from getting saved.

2) Have a hidden variable in your DCT which can be set from Callserver program through JavaScript (ex: values could be true, false).

3) Have a JavaScript function (ex: resumeSave())in DCT which will be called in Callserver program in the end. When the callserver calls the DCT function (resumeSave) it is an indication that Callserver program has finished its job.

4) Inside this userdefiend function resumeSave(), first access the hidden variable value that was set in 2), and then based the value decide to continue the save the DCR. Now DCT itself will not get saved, because in OnSaveValid we had returned false which had indicated all save operation to stop. Hence we would need explicitly call IWDatacapture.save() inside this function. Once this call is executed DCR gets saved, and also OnSaveDone() event get triggered and you can perform any other operations you would like to perform here.

ISCBorisB

Here is how I had done in one the implementation...

That'll work if everything goes as it should. One missing step in this approach is cancelling a callout that takes too long to return or does not return at all.
Before returning false from saveValid you may want to setTimeout to cancel hanged call, Something like the following:

var timeoutID = 0;

function saveValidHandler {
   ...
   IWDatacapture.callServer(service, parameters, false);
   timeoutID = window.setTimeout("cancelRemoteCall()", 60000); // One minute Time-Out
   return false;
}

// Abort the request by sending a blank page to the hidden frame.
// Subsequent calls to callServer() will cancel any previous calls.
function cancelRemoteCall() {
   IWDatacapture.callServer("blank.html", new Object(), true);
   alert('Warn your User that Save has failed');
   timeoutID = 0;
}

// This is callServers' call back Function 
// Do not forget to Clear timeout so that we won't have false saving alarms
function resumeSave() {
   if (timeoutID) {
      window.clearTimeout(timeoutID);
      timeoutID = 0;
   }
   ...
   IWDatacapture.save();
   ...
}