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

Another callserver question.

namithapai

I know there have been several callserver questions already. I promise I have read all of them and also the manual several times over. Please help with my problem.

I am trying to simply implement the "locations" callserver example from templating. After picking the region, I see the IWDatacapture.displayMessage which says retrieving from the region selected. After that nothing happens.

How can I debug what is happening with the server call?.
the callserver statement is
IWDatacapture.callServer("http://myserver/iw-bin/getLocations.ipl",
params);
which is apparently not reaching the server.

Find more posts tagged with

Comments

Adam Stoller

I know there have been several callserver questions already. I promise I have read all of them and also the manual several times over. Please help with my problem.

I am trying to simply implement the "locations" callserver example from templating. After picking the region, I see the IWDatacapture.displayMessage which says retrieving from the region selected. After that nothing happens.

How can I debug what is happening with the server call?.
the callserver statement is
IWDatacapture.callServer("http://myserver/iw-bin/getLocations.ipl",
params);
which is apparently not reaching the server.

From there - if the script gets called, you need to verify that the parameters get passed correctly. If the script doesn't get called, well - post again and maybe someone will have some other ideas.

namithapai

Yes, tried all the above. Script does not get called. When I try the script directly from browser or through command line it works fine.

Is there some permission issue?

I have access as "root" on the server where I am executing and works fine.
I have access as "master" in teamsite and looks to be ok from browser once I am logged into the same session.
Using same access as master for "new form entry" , but callserver does not get executed.

Pawan

Yes, tried all the above. Script does not get called. When I try the script directly from browser or through command line it works fine.

Is there some permission issue?

I have access as "root" on the server where I am executing and works fine.
I have access as "master" in teamsite and looks to be ok from browser once I am logged into the same session.
Using same access as master for "new form entry" , but callserver does not get executed.

When you are running the script from the browser or the command-line, you may be hard coding the arguments, they may not be getting through when inside a dcr, please verify that.
Regarding the permissions issue, Ghoti already said how to debug it. Make a copy of the file, set 755 permission on it and debug with it.

ISCBorisB

Yes, tried all the above. Script does not get called. When I try the script directly from browser or through command line it works fine.

Is there some permission issue?

I have access as "root" on the server where I am executing and works fine.
I have access as "master" in teamsite and looks to be ok from browser once I am logged into the same session.
Using same access as master for "new form entry" , but callserver does not get executed.

If your code is identical to the IWOV sample nothing should happen on "New Form entry". Sample is configured
for certain "onItemChange" Event (I just looked). Get to "location/region", modify it and change Focus.
If your code differs from the sample post it if you need help

namithapai

Yes, code is identical to sample.

Yes, I have changed/selected the region and that is when the onchange event needs to be triggered which has the callserver to getLocations.ipl

The datacapture display message shows that the formapi function for fetching locations(callserver) has been invoked. That is where it stops.

namithapai

Problem solved. Had a special character "_" in the perl executable path :-) duh right?

Anyway this was just a sample to see why my other perl script with database call was not working. Finally nailed it down to some ENV settings that were conflicting. This stopped the params from getting through and caused all the heartache.