DMT - Add Memo Table Record - Unable to call method

Kinetic ERP
,
21

Not sure what the issue would be, did you add a memo to a job and then look at the record in the memo table before trying to create a DMT template?

22

Yes, I created several memos in various jobs to get a good idea of what other fields might be used. I used the same set of fields and am getting that weird error. The error doesn’t seem to point to a bad field, it is suggesting that the method is not available. Still waiting on Epicor support.

23

I wonder if the GUID is what is stopping me up here. I see other threads where folks can’t create Memos. In this thread, Brandon talks about creating a GUID in a BPM. Please tell me I don’t have to go this far just to add in a memo!?

Populating records with DMT, need GUID? - ERP 10 - Epicor User Help Forum (epiusers.help)

I even tried exporting the Memo table to excel from the BAQ (including the properly labeled field names). Then I just replaced the data with my data. I still get the same error. It is like the DMT just doesn’t do memos for some reason!

24

Hi Nate,
In reading through this post, a few questions came to mind that were not explicitly stated so here are my questions:

  1. Are there any security provisions (menu, field or Process) in either Job creation/updating or in memo creation or any Directives that might be driven by specific users or groups?
  2. Do you have and use a specialty DMTUserID and is that configured to allow DMT (newer versions User sec checkbox on Options tab)?
  3. Memo is a one table to many table relationship so in order to create the memo, it requires that foreign key field from Job, in this case. If it get that from the Job table, and a job is not fully engineered and released, would that inhibit the DMT getting what it wants from each job record in terms of that foreign key?
  4. Are your jobs always single assembly or do you have a hierarchical assembly structure and is the memo always to be linked at the same level (presumably assembly 0 level) i.e. does assembly level become a necessary element for establishing the relationship between Job and Memo tables (or any subordinate job table for that matter)?
25

Hello Henry,
All good questions!

  1. No special security or directives in place.
  2. No special DMT user.
  3. I am referencing the job sysrowid in the RelatedToSysRowID field. I used the same GUID as other memos saved for this job.
  4. Jobs can be either single or multi-assembly. In my testing it doesn’t seem to matter to DMT which kind of job I try to submit a memo for. The error message is always the same.

FWIW, my Epicor tech got back to me and said he also reproduced the error. I have submitted a case and waiting on a problem. I am thinking that when I use DMT to update all of our open jobs, I am going to have to skip the memo step. I really wanted to document the fact that I used DMT to update each open job, but DMT isn’t the silver bullet they sold us!

In the future, if they do get the DMT fixed for memos, I could always resubmit my intended job memos with backdated MemoDates. I think that is my plan going forward. Skip the memo for now, and add it later if Epicor can fix DMT.

Thanks for the suggestions!

26

Epicor support could not provide a solution. They opened a problem for this case: PRB0242993.
They also added a development task: TASK7200290. Which makes me hopeful that they will fix this one. I will post back if I hear anything new.
Thanks!

1 Like
27

Nice, sorry to hear this. Glad they acknowledged it and are trying to fix it.

28

I know it’s 3 years later but have you heard back from this case ? I’m trying just now to do the same thing and had the same problem as yours when adding via DMT for memo related to jobhead