Web call to Landmark call (Variable Change in Landmark database)

Hi Shane,

I haven't done this myself, so tread cautiously, but hopefully this will help.

In Landmark, each prodline has it's own set of PFI data which stands alone (users, tasks, config settings, triggers, workunits, variables, etc), so you would run it against "prod" rather than "gen". 

Also, the keys for this table are PfiWorkUnit and PfiWorkUnitVariable, and you should only include fields that need to be updated. I would exclude SeqNbr completely, since it isn't a key and it won't be updated (I assume).  The same applies to VariableType and UniqueID.

I'd try something like this:

_dataArea="prod" & _module="pfi" & _objectName="PfiWorkunitVariable" & _actionName="Update" & _actionOperator="NONE" & _actionType="CreateUpdateDelete" & _runAsUser="" & _pageSize=25 & PfiWorkunit="{workunit}" & PfiWorkunitVariable="New_Pay" & VariableValue="{new value} "

I hope this is helpful.  Good Luck.

Kelly

I looked at some of mine (that were migrated from PFI), and I also have:
&VariableType="1" &SeqNbr="1"

Also, beware that the current (10.0.3.CU11, CU13, CU14, AFAIK) transaction builder is broken for some of the "pfi" objects, including PfiWorkunitVariable object

Oof!  John - are you saying that all the PfiFlowVariable transactions have been changed to update VariableType to 1 and SeqNbr to 1?  I'd think that would NOT be good...

Thanks for the info on the CU issues too - I hadn't heard that.  Do you happen to have any details - KB numbers or anything?  Thanks!

Posted By Woozy on 07/22/2013 11:36 AM
Oof!  John - are you saying that all the PfiFlowVariable transactions have been changed to update VariableType to 1 and SeqNbr to 1?  I'd think that would NOT be good...

No, I'm not saying that they are changed, I'm saying that those fields/values were in the original web call and are converted

Whew! Thanks for the clarification, John. Of course the CU issue is still concerning.

Based on my case notes, I think the CU issues were related to having different CU levels on the Landmark server vs. the designer; this is particularly a problem when new releases come out, and older versions are not left on the download site; e.g. IPA/LPA server was 10.0.3.CU11 and only designer on the download site is 10.0.3.CU13. In that case, the pfi object definitions change and the designer can not load them. JT-470190 - supposedly corrected in "latest version" of 10.0.4.
Also, a workaround that works sometimes, but not always:

The 'local class incompatible' error was being thrown because the type.jar file on your IPDesigner installation folder was incompatible with the type.jar file on your server.
To resolve this we did the following.
Step 1: Shut down the Infor Process Designer (IPD) on PC.
Step 2: Went to the IPD install\lib\jar directory on PC and rename the type.jar file to type.jar.bak.
step 3: On the Landmark server went to the $LAENVDIR\java\jar directory and copied type.jar
step 4: Pasted the type.jar file from the Landmark server into the IPD install\lib\jar directory on PC (from step 2).

Excellent- Thanks John! (Sorry for hijacking the thread a bit, Shane!)