x Want to participate? Join the group to interact
  • State Verified Answer
  • +1 person also asked this people also asked this
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 140 subscribers
  • Views 2010 views
  • Users 0 members are here
Browse Forums
Announcements
237
topics
29
replies
General Discussion
5k
topics
13k
replies
Sage Data & Analytics
56
topics
95
replies
Sage Enterprise Intelligence
211
topics
418
replies
Sage Intelligence Reporting
121
topics
322
replies
Bense

Function cannot be called in this context

SOLVED
Posted By

Hello everyone Slight smile

I built a generic screen "ZTRANSPORTCO" for a customer. The screen is used in multiple windows.

The problem is when I try to "Jump to" another window which also has a tab with the generic screen "ZTRANSPORTCO" I get the following error:

When I remove the generic mask from the tabs in the window of the customer the error no longer occurs.

I know it would be possible to just copy the mask and use this mask with the same specific script in the customer window. But this way we have to maintain two masks.

Would it be possible to open the tab in the customer window with another alias? So that I can use the same mask for both windows without duplicating?

Has anybody an idea for a possible solution without duplicating the generic mask?

Thank you in advance.

Kind regards 

Parents
  • +1
    verified answer

    Hi Bense, I found a couple KB articles that discuss this error, which is a generic error;

    • The root cause is Sage X3 is launching a function or task and that function/task is trying to open a screen that already exists in memory.
    • The error can occur if there is any underlying function that the previous user did not close correctly.

    As you're initialing a screen that is in use in both areas then there is potential to get this error as its already tied up in memory.

    There may be solutions available to avoid this without having to duplicate the mask but as that is custom you'd need to work with a partner or your local coex team for possible resolutions.

    Thanks 

Reply
  • +1
    verified answer

    Hi Bense, I found a couple KB articles that discuss this error, which is a generic error;

    • The root cause is Sage X3 is launching a function or task and that function/task is trying to open a screen that already exists in memory.
    • The error can occur if there is any underlying function that the previous user did not close correctly.

    As you're initialing a screen that is in use in both areas then there is potential to get this error as its already tied up in memory.

    There may be solutions available to avoid this without having to duplicate the mask but as that is custom you'd need to work with a partner or your local coex team for possible resolutions.

    Thanks 

Children

*Community Hub is the new name for Sage City