Open Forum

Expand all | Collapse all

Smartconnect JE Map with MDA

Jump to Best Answer
  • 1.  Smartconnect JE Map with MDA

    Posted Jul 14, 2021 01:00 PM
    Hey there,

    i'm trying to get the Smartconnect JE map with MDA working but it seems to stumble upon the MDA field.
    it says the 'taUpdateMDA' store procedure does not exist.  I talked to eone who said this was a custom SP, but since it is comes with the application, doesn't that sound like a bug instead?
    thx.

    ------------------------------
    Toulou Yong
    Senior software engineer
    Arch Insurance Group Inc
    Raleigh NC
    ------------------------------
    Academy - Online Interactive Learning from Experts


  • 2.  RE: Smartconnect JE Map with MDA

    SILVER CONTRIBUTOR
    Posted Jul 15, 2021 09:19 AM
    there may be a permission issue with that SP if it does exist. did you confirm it's on the specific DB? if it is there, you might need to run the Grant.sql code to make sure it's available to proper groups.

    ------------------------------
    Mike Bresnan
    Arabella Advisors
    Washington MD
    ------------------------------

    Academy - Online Interactive Learning from Experts


  • 3.  RE: Smartconnect JE Map with MDA

    Posted Jul 15, 2021 09:40 AM
    From your screenshot in your case a few months ago (looks like you have been working on this a while) and then your chat a couple days ago where you confirmed the error - the error from SmartConnect (which is coming from the eConnect API which is calling the proc in SQL for you) is actually:

    Error


    So similar name but not 'taMdaUpdate' which is the out of the box eConnect MDA proc.

    Now Mike could be correct in that it is permissions to the proc, but I don't suspect it is as typically SQL would give you a specific permission denied error and not "i can't find this proc".

    More likely the error is his other suggestion - if you look in the target company db.  IS the proc there?  Because if not, then we would expect this.
    The other possibility is that it does exist - but the schema is set to something other than dbo.  eConnect is expecting the schema for all the procs it calls to be dbo.

    Since this is NOT out of the box GP eConnect, you would have to find a copy of the proc from somewhere in order to put it into your GP company folder to be called by the eConnect API.

    And if you can't find it anywhere - your options are now limited to:

    1. don't use it, just use the out of the box taMdaUpdate proc (which i assume doesn't do what you want otherwise why would you have a custom version?)
    2. you have no choice but to rewrite the proc again

    patrick
    eOne



    ------------------------------
    Patrick Roth
    eOne Solutions
    Fargo
    ------------------------------

    Academy - Online Interactive Learning from Experts


  • 4.  RE: Smartconnect JE Map with MDA

    Posted Jul 15, 2021 10:30 AM
    I checked in all of our 100+ databases and it is nowhere in sight.
    Would a GP SQL maintenance be able to recreate it?

    ------------------------------
    Toulou Yong
    Senior software engineer
    Arch Insurance Group Inc
    Raleigh NC
    ------------------------------

    Academy - Online Interactive Learning from Experts


  • 5.  RE: Smartconnect JE Map with MDA

    Posted Jul 29, 2021 12:41 PM
    Right, but where does that SP come from and how would we re-write it?
    thx.

    ------------------------------
    Toulou Yong
    Senior software engineer
    Arch Insurance Group Inc
    Raleigh NC
    ------------------------------

    Academy - Online Interactive Learning from Experts


  • 6.  RE: Smartconnect JE Map with MDA

    Posted Jul 15, 2021 11:38 AM
    SQL Maintenance doesn't recreate "core" GP procs - it only allows you to recreate the zDP "table" procs that Dex/GP uses for table access.

    You are thinking of the DBMaintenance.exe utility - that WOULD recreate all the procs/functions in SQL per product in GP.

    But in this case, that won't help you here either since your proc is "Custom".  And again I would assume it IS custom because the name isn't taUpdateMDA - it is taUpdateMDA_SC.

    Now I suppose you could have just renamed the existing taUpdateMDA proc to that - but I don't see what purpose that would accomplish other than causing problems so seems unlikely.

    Since it is custom - the only way to get it back again would be to find a copy of it somewhere on the system or somebody's machine or something.  Or, I suppose, you could find an old SQL backup of the GP company db's and see if you find it there and at least get a version of it and go from there.

    Still, it is puzzling that you would have this custom proc and therefore a custom SmartConnect node to use it.  And then don't actually have the proc anywhere.


    ------------------------------
    Patrick Roth
    eOne Solutions
    Fargo
    ------------------------------

    Academy - Online Interactive Learning from Experts


  • 7.  RE: Smartconnect JE Map with MDA

    Posted Jul 15, 2021 02:57 PM
    Yes, it is kind of weird.
    another option would be to duplicate the node with node builder and publish it in dev.
    then take that SP and reproduce it in DEV with the correct naming convention?

    ------------------------------
    Toulou Yong
    Senior software engineer
    Arch Insurance Group Inc
    Raleigh NC
    ------------------------------

    Academy - Online Interactive Learning from Experts


  • 8.  RE: Smartconnect JE Map with MDA

    Posted Jul 15, 2021 05:28 PM
    Well, Node Builder lets you create new nodes - you can't duplicate existing ones.  And even if it could, you don't want the existing one anyway or else you would have been using it.

    But since you brought "Node Builder" into the picture, it would seem likely that your node is there.  You should launch Node Builder and assuming it is attached to the NodeBuilder database still, your mystery node is very likely there.

    And if so, then you can publish it with SmartConnect (making sure to not mark the publish to SmartConnect checkbox) and it'll publish to the SQL dbs.

    However, you won't be able to take that proc because we publish them encrypted and SQL won't let you script that out.  So you would have to publish to the company destinations where you want to use it.

    ------------------------------
    Patrick Roth
    eOne Solutions
    Fargo
    ------------------------------

    Academy - Online Interactive Learning from Experts


  • 9.  RE: Smartconnect JE Map with MDA
    Best Answer

    Posted 17 days ago
    I wanted to follow up and bring closure to this case:
    So it looks like eOne was right and the store procedure was indeed custom (taUpdateMDA_SC).  I had to reconnect with a colleague elsewhere and he confirmed that he did not have that SP @ his organization either.  So clearly, the partner came up with it, and they had to dig the SP up as well, since they had lost track of it.  Once they found it, we ran the SP on the pertinent companies but there were tweaks involved still.  So after several modifications in the SP and the Smartconnect map, we were able to get the JE with MDA map running but another requirement was necessary:

    the qty box needed to be checked on the Account Analysis Defaults window.  (quick update on DTA00300 table/ DTA_Quantities columns).
    Once this was taken care of, the map ran properly.
    thx.




    ------------------------------
    Toulou Yong
    Senior software engineer
    Arch Insurance Group Inc
    Raleigh NC
    ------------------------------

    Academy - Online Interactive Learning from Experts


If you've found this thread useful, dive deeper into User Group community content by role