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 1970 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
210
topics
416
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 

  • +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 

  • +1
    verified answer

    In cases like this, we open the new object in a new tab, that way it will no conflict with the previous.

  • 0 in reply to NevilleC

    Hello ,

    Thank you very much for your reply Slight smile

    It would be interesting to find a solution with the COEX. But for the moment I think we will in this case use the duplication.

    Thank you once again.

    Kind regards

  • 0 in reply to Martins de Almeida

    Hello ,

    Thanks a lot for your reply Slight smile

    Good idea with opening the new object in a new tab. 

    Unfortunately our customer wants to use the "Go to" tunnel for going to the other function and I think there is no action executed when clicking "Go to". At least no object action seems to be called and I also think there is no field action for it. Please correct me if there is one.

    It would be  probably possible to place an icon / symbol next to the field. When the icon gets clicked we could open the object in a new tab.

    Thank you for your help.

    Kind regards

  • 0 in reply to Bense
    SUGGESTED

    You can add this to the 3 dots you have next to the field, or as you say with an extra icon, second option occupies more space in the screen, first option makes you do an extra click.

  • 0 in reply to Martins de Almeida

    Both are good options thank you. I think adding an option to the 3 dots icon would be done with a button field action.

    For this customer we had to use the standard tunnel icon. Therefore we copied the masks for the different windows in order to solve the problem. Nevertheless good to know that they are other options. Thank you.

*Community Hub is the new name for Sage City