web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

I am trying to do customization using Dexterity in DynamicsGP Manufacturing Module ICONMFG.DIC, how can I access the resources from the dictionary Dynamics.dic in my customization of Manufacuring Module ICONMFG.DIC. Can anyone help me please .....?

(0) ShareShare
ReportReport
Posted on by

Dexterity-_2D00_-ICONMFG_5F00_1.DIC.jpg See the error msg I get when I am trying to access resources from Dynamics.DIC dictionary

*This post is locked for comments

I have the same question (0)
  • Tim W Profile Picture
    2,925 on at

    You can't do it the way you're trying to do it, it's a tier issue.  MFG is a custom product off Dynamics.dic and GP inheritance from Dex is only two tier.  Your custom product would need to be built off Dynamics.dic instead and then you need to build references (cross dictionary triggers) across to the MFG dictionary.

    There are some tricks to working peer to peer, many things you can accomplish, some things are limited.  Everything I know about this process I've learned from David Musgrave.  https://blogs.msdn.microsoft.com/developingfordynamicsgp/2009/09/17/understanding-cross-dictionary-dexterity-development/

  • Tim W Profile Picture
    2,925 on at

    Here's a sample of some logic to set a value in the RMA window and run a script in that dictionary.  Functionality is restricted and it's really a drag to test it but you can build control and workflow into a 3rd party with triggers (using ByName) similar to working against the Dynamics dictionary.  When you want to modify a window though you have to blend your code with VBA so I just say no when asked :).

    Good luck to you on your quest.

    Trigger script


    if Trigger_RegisterFocusByName(949, "window SVC_RMA_Create_Return of form SVC_RMA_Create_Return", TRIGGER_FOCUS_ACTIVATE, TRIGGER_AFTER_ORIGINAL, script CI_RMA_Set_Return)
     <> SY_NOERR then  
     warning "Focus trigger registration failed ";
    end if;

    Cross dictionary logic.

    {CI_RMA_Set_Return}

    local text code;
    local string compiler_error;
    local string l_RMA_Invoice;
    local string IN_Value;

    if empty(Launch_GetFileName()) then
     warning "Service Management is not loaded";
     abort script;
    end if;
    if Launch_GetProdPosition(949) < 1 then
     warning " Service Management is not loaded.";
     abort script;
    end if;

    IN_Value = "RTN";

    {Build the pass-through sanScript code.}
    clear code;
    code = code + "in string IN_Value;";
    code = code + "if isopen(window SVC_RMA_Create_Return of form SVC_RMA_Create_Return) then";
    code = code + "  set 'Document ID' of window SVC_RMA_Create_Return of form SVC_RMA_Create_Return to IN_Value;";
    code = code + "  run script 'Document ID' of window SVC_RMA_Create_Return of form SVC_RMA_Create_Return;";
    code = code + "  focus 'Customer Number' of window SVC_RMA_Create_Return of form SVC_RMA_Create_Return;";
    code = code + "end if;";

    {Execute the code.}
    if execute(949, code, compiler_error,IN_Value) <> 0 then
     {A compiler error occurred. Display the error.}
     error compiler_error;
     abort script;
    end if;

  • Suggested answer
    Almas Mahfooz Profile Picture
    11,009 User Group Leader on at

    So where you are actually creating this function, in fresh Dynamics,dic for your customization or in manufacturing dictionary?

    If in fresh dynamics.dic then you must not have this error.

    If in manufacturing dic then did you merge it with dynamics.dic?

     

  • MG-16101311-0 Profile Picture
    26,225 on at

    Tim is right on the money. You cannot use the manufacturing dictionary as your base development dictionary. All your work needs to be done in a clean Microsoft Dynamics GP dictionary, DYNAMICS.DIC. You will need to implement cross-dictionary triggers and other techniques to be able to retrieve the information you want.

    The problem you have with adding resources to the manufacturing dictionary is, a) you cannot deliver a manufacturing dictionary containing your customizations as this is in violation of Microsoft's licensing agreements, b) you cannot easily extract your customizations using the standard Dexterity Utilities tools.

    If you need more information on cross-dictionary development, please don't hesitate to reach out.

  • Suggested answer
    David Musgrave MVP GPUG All Star Legend Moderator Profile Picture
    14,095 Most Valuable Professional on at
  • Community Member Profile Picture
    on at

    OK I will try.

    Thanks Tim WAlmas MahfoozMariano Gomez and David Musgrave for your quick reply.. :-)

  • Almas Mahfooz Profile Picture
    11,009 User Group Leader on at

    you are welcome:)

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
mtabor Profile Picture

mtabor 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans