6/29/2025 1:32:02 PM
|
| |
| slxdeveloper.com Community Forums |
|
| |
|
|
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
Forum to discuss the use of the SalesLogix Web Platform, Client and Customer Portals, and the Application Architect (For version 7.2 and higher only). View the code of conduct for posting guidelines.
|
|
|
|
Add Opportunity Attachment
Posted: 23 Sep 10 5:36 AM
|
Hi All,
We are getting an error when trying to add a HTML attachment to an opportunity, is this a known issue?
Thanks. |
|
|
|
Re: Add Opportunity Attachment
Posted: 23 Sep 10 5:51 AM
|
Hi,
What's error? Also, what version of SalesLogix Web are you running?
I have just tested this on v7.5.2 and SP3 and it works fine. |
|
|
|
Re: Add Opportunity Attachment
Posted: 23 Sep 10 6:00 AM
|
Its 7.5.2 but we dont have SP3 yet. The error is An exception occurred executing the dynamic method
Attachment InsertFile/Attachment |
|
|
|
Re: Add Opportunity Attachment
Posted: 23 Sep 10 6:10 AM
|
I have just located a known defect, it looks like it could be your issue..?
Existing Defect ID: 1-72258
Case Number: 4421821
The web client is not generating ATTACHID on the same base as the lan client. As a result it is causing primary key conflicts.
Symptoms on the web client are a message:
An exception occurred executing the dynamic method Attachment.InsertFileAttachment.
In the log there will be a message reflecting the primary key conflict.
You can not reproduce the exact symptom on the Eval database, however you can readily identify the issue.
* Attach a file from the Web client
* Attach a file from the Lan client
* The web client attachment gets saved with ATTACHID = QDEMOA000001
* The LAN client attachment gets saved with ATTACHID = QDEMOA000FZA
The reason is the LAN client is using keytype 25, the web client is using keytype 37.
As a work around, bump up the keyvalue on the keytype 37's record (and hope they don't catch up until Sage releases the actual fix)
Additional Info:
This will be addressed in SP3 (consistency). The Web does use a different Key Type for attachments (37) than the LAN (25). This may cause a failure when they collide - but there is a simple workaround for now. Using a different value is not a problem in itself. We will fix the inconsistency moving forward.
This also occurs in 7.2.2, 7.5.0, and 7.5.1. The workaround is below:
Workaround: bump the 37 ID way over the 25 ID.
Example: If 25 ID is at ‘A006Y7T’, bump the 37 ID to ‘AA06Y7T’
|
|
|
| |
|
You can
subscribe to receive a daily forum digest in your
user profile. View the site code
of conduct for posting guidelines.
 Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
|
|
|
|
|
|
|
|