Reset current "Initial Interchange control number (ISA 13)" in X12 EDI connector.
Connector keeps internally (using default ObjectStore) the last sent value, to be able to increment it on each execution. ObjectStore keys start with sender qualifier, then sender id, then receiver qualifier, then receiver id, etc., for example:
ZZJOHNSON075400110000009*JOHNSON540011000DSD
Initial Interchange control number (ISA 13) is configured using element "initialInterchangeNumber" in X12-EDI config, for example:
For Mule 3
<x12-edi:config name="X12_EDI"
doc:name="X12 EDI"
initialInterchangeNumber="10000"
sendUniqueGroupNumbers="true">
</x12-edi:config>
For Mule 4
<x12:config name="X12_EDI_Config"
doc:name="X12 EDI Config" doc:id="8723f51f-e339-4724-bca2-fd0049cce5db"
initialInterchangeNumber="10000" />
To reset ISA13 number to the initial value:
Studio
Start application with option "Clear application data" (Right click on your project, then go to Mule, then navigate to "Clear Application Data.")
Standalone
Connector doesn't provide a method to update key/values in the internal objectstore, to reset this value you should implement a flow to edit those values
CloudHub
Delete key/values from Runtime Manager, see "Viewing Application Data"
Manage Application Data Storage with Object Stores
001117926

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.