An Email Conversation Between Phil and Jonas

Hi Phil,

The change is scheduled for NEXUSe2e 4.6.0 version, which is not scheduled for release yet. I'll discuss with the development team if we should make a patch available that enhances the id length fields. In the meantime, this must be fixed directly on the DB layer.

Please let me know if you know more NEXUSe2e users running into truncation issues. 

Best regards,
Jonas

Am 27.01.2012 um 16:51 schrieb Jones, Phil:

Hi Jonas,

Thank you for your quick response. I think this will solve my problem.

Do you have any idea when the new release which corrects the length of these fields will be available? Do think this will be made available in a patch for other Nexuse2e users running into the same issue. 

Thanks,
Phil

From: Reese, Jonas

Hi Phil,

Sebastian is not in our office today, that's why I am answering your request.

The maximum length for conversation and message IDs is 96 characters.

To solve your problem, you can increase directly on your DBMS with an SQL statement:

ALTER TABLE nx_message MODIFY message_id varchar(256)

ALTER TABLE nx_conversation MODIFY conversation_id varchar(256)

The configuration within NEXUSe2e that creates the schema cannot be changed easily, but once the length constraint is changed, NEXUSe2e will not reset it to the configured value.

We will increase the default size for future releases to 256 characters.

Hope this helps to solve the problem. If not, let me know.

What do you mean with CPA? 

Best regards,
Jonas

Am 27.01.2012 um 01:44 schrieb Jones, Phil:

Hello Sebastian,

I am testing an inbound ebxml from a non NexusE2E trading partner and the message fails in the background.

It appears that either the Conversation-id or Message-id is too long for Nexuse2e to handle. I am able to get the message if I shorten the Message-id and Conversation- ids.

4.4.4, revision: 1052, build: 61 2010-04-09_11-12-04

Example of ids coming in.

<eb:ConversationId>11.BizLink.3.3.0.68.69cecaa1-0210-4467-983f-612397e3e986.f9f6591f-486a-11e1-8be1-c77777fa3347@412c1e5c2f1365d6.5539422e.1350c8ad690.7fc8</eb:ConversationId>

<eb:MessageId>ebXML.11.BizLink.3.3.0.68.4e33ae99-907d-4a69-9b0e-d4d6af568bf5.f9f65920-486a-11e1-8be1-c77777fa3347@412c1e5c2f1365d6.5539422e.1350c8ad690.7fc7</eb:MessageId>

Example of Nexuse2e

<eb:ConversationId>3b34220c-4d50-4fcd-99dd-c18f523879cf</eb:ConversationId>

<eb:MessageId>5d49a97c-b5aa-4259-aad2-121e6d6d6f07</eb:MessageId>

How long can these Ids be? Can this be configured?

Does Nexus support CPAs?

Thanks,
Phil Jones
Agrium Inc.