Prev
Next
Forums Integration / Customization IPA/ProcessFlow

Update configuration settings via IPD

 6 Replies
 1 Subscribed to this topic
 52 Subscribed to this forum
Sort:
Author
Messages
Steph76
Basic Member
Posts: 18
Basic Member
3/31/2020 4:22 PM

    Hello,

    I have a pf where with a starting payment number that I need to keep track of and increment each time the pf runs. I created a variable in my configurations on LM and I'm using a Landmark Transaction node to update it. I get the value of the configuration property and set it to a local value and increment by 1. Then I try to set the configuration property to the local variable value. I get the following error when trying to run it.

    Activity Error com.lawson.rdtech.type.ViewException: Remote call failed: com.lawson.rdtech.type.ServiceAction; local class incompatible: stream classdesc serialVersionUID = -5855575179992000011, local class serialVersionUID = -5134494559472712660

    I'm not sure what's wrong. Can someone tell me if I'm missing required fields? Do the dates have to be filled in?

    _dataArea="<!--appProdline-->" & _module="pfi" & _objectName="PfiConfigurationProperty" & _actionName="Update" & _actionOperator="NONE" & _actionType="CreateUpdateDelete" & _runAsUser="" & _authenticatedUser="" & _pageSize="30" & _relationName="" & _setName="" & _asOfDate="" & _effectiveDate="" & PfiConfiguration="MyConfig" & PfiConfigurationProperty="GlobalPayNum" & Value="<!--val1-->"

    David Williams
    Veteran Member
    Posts: 1127
    Veteran Member
    3/31/2020 4:43 PM
      _dataArea="mydataarea" & _module="pfi" & _objectName="PfiConfigurationProperty" & _actionName="Update" & _actionOperator="NONE" & _actionType="CreateUpdateDelete" & _runAsUser="" & _authenticatedUser="" & _pageSize="30" & _relationName="" & _setName="" & _asOfDate="" & _effectiveDate="" & PfiConfiguration="system" & PfiConfigurationProperty="Test" & Value="1"

      I tested this and it worked fine.
      David Williams
      FireGeek21
      Veteran Member
      Posts: 84
      Veteran Member
      3/31/2020 4:47 PM
        Steph,

        I do this all the time - very helpful to be able to write to the configurations!

        Remote call failed tells me you don't have a "Configuration Name" filled in (drop down box above where you put in the transaction string).

        I see you have <!--val1-->. Are the --'s part of your variable name? I am thinking these should be removed because <!-- and --> are considered a leading trailing remark tag in html.

        Here is a sample of a transaction string I have that works.

        _dataArea="" & _module="pfi" & _objectName="PfiConfigurationProperty" & _actionName="Update" & _actionOperator="NONE" & _actionType="CreateUpdateDelete" & _runAsUser="" & _authenticatedUser="" & _pageSize="30" & _relationName="" & _setName="" & _asOfDate="" & _effectiveDate="" & PfiConfiguration="BusinessAdmin" & PfiConfigurationProperty="EpicRefundACK_LastRun" & Value=""

        Tammy
        FireGeek21
        Veteran Member
        Posts: 84
        Veteran Member
        3/31/2020 4:50 PM
          Sorry, seems the site change my code to Value="". I actually have < ! newValue > in quotes. I hope by adding spaces you can see what I actually have in that Value=... piece of the transaction.

          I truly believe it may be the Configuration Name - or - maybe your connection timed out.
          Steph76
          Basic Member
          Posts: 18
          Basic Member
          3/31/2020 4:52 PM

            I was running it locally. That seemed to be the problem. Once I uploaded the PF to LM and ran it worked. Were you able to run it local?

            Steph76
            Basic Member
            Posts: 18
            Basic Member
            3/31/2020 4:58 PM

              FireGeek21,

              The editor must have put in the dashes when I copied in my code. I had the Configuration Name drop down set to the one I was going to update. I change it to system since I specify which Configuration Name I want to update in the path/string. Didn't seem to make a difference when runnng it locally.

              FireGeek21
              Veteran Member
              Posts: 84
              Veteran Member
              3/31/2020 5:39 PM

                I cannot run it locally.  If I have any connection to the Lawson/Infor, I cannot run it locally unless I bypass that Lawson/Infor connection.  For testing purposes, I run this through our Dev system until I have all the kinks worked out.

                I do have a "sandbox" pflow where I work out pieces of larger pflows like javascript, sql, etc.

                Glad you found the issue.


                Tammy