x Want to participate? Join the group to interact
  • State Not Answered
  • Replies 6 replies
  • Subscribers 78 subscribers
  • Views 993 views
  • Users 0 members are here
Browse Forums
Announcements
106
topics
32
replies
General Discussion
6k
topics
18k
replies
nins93

Sage CRM Task Launcher

Posted By

We have inherited some bespoke form launching developed by a former BP. I get the following error when trying to Amend a Purchase Order:

The bespoke xml file in the TaksLauncher folder has the Purchase Order form defined as below:

<?xml version="1.0" encoding="utf-8"?>
<remoteForms>
<form
id="6601"
name="Sage.MMS.POP.AmendPurchaseOrderDetailsForm"
objectType="Sage.Accounting.POP.POPOrder"
assembly="Sage.Accounting.Commercials"
/>
</remoteForms>

and the custom asp that calls this has the following url defined:

<a class="er_buttonItem" href="javascript:FormLaunch('">localhost:8088/.../LaunchForm.Open id="Button_PurchaseOrder">Purchase Order</a>

Can anyone suggest what is wrong? This works on a previous version of CRM

Parents
  • 0

    The form launcher is just using the normal Sage 200 'Role' security to test whether or not the user has access to the specified form. In a typical out-of-the-box Sage 200 installation, there won't actually be a feature target for Sage.MMS.POP.AmendPurchaseOrderDetailsForm. There *will* be a target for Sage.MMS.POP.AmendOrderForm, as this is the one that you find on the standard menu, which in turn will launch Sage.MMS.POP.AmendPurchaseOrderDetailsForm. The solution is to manually add a feature in SAA with a target of Sage.MMS.POP.AmendPurchaseOrderDetailsForm and authorise it as required.

    As for the form launcher having a dependency on IE...well, kind of. The task listener process does use the InternetSetCookie method from the WinInet API - which of course is an IE thing - but it only needs to do so if it's running in multi user mode (as it would be on Terminal Server). In single user mode it should just keep on trucking.

Reply
  • 0

    The form launcher is just using the normal Sage 200 'Role' security to test whether or not the user has access to the specified form. In a typical out-of-the-box Sage 200 installation, there won't actually be a feature target for Sage.MMS.POP.AmendPurchaseOrderDetailsForm. There *will* be a target for Sage.MMS.POP.AmendOrderForm, as this is the one that you find on the standard menu, which in turn will launch Sage.MMS.POP.AmendPurchaseOrderDetailsForm. The solution is to manually add a feature in SAA with a target of Sage.MMS.POP.AmendPurchaseOrderDetailsForm and authorise it as required.

    As for the form launcher having a dependency on IE...well, kind of. The task listener process does use the InternetSetCookie method from the WinInet API - which of course is an IE thing - but it only needs to do so if it's running in multi user mode (as it would be on Terminal Server). In single user mode it should just keep on trucking.

Children

*Community Hub is the new name for Sage City