ARS1129E - Revision history

Jderrick: Added a note to remove extra space characters or tabs around the date fields for ARS1129E.

2025-03-05T17:27:28Z

Added a note to remove extra space characters or tabs around the date fields for ARS1129E.

← Older revision		Revision as of 17:27, 5 March 2025
Line 25:		Line 25:
	== Troubleshooting ==		== Troubleshooting ==
	Using the Row number in the error message, check the Generic Index file to determine which field the error relates to. Then, using the IBM CMOD Administrator Client to update the date format to match the format of the data itself. In the case of this example, remove the dash ("-") characters from the date format string, and attempt the load again.		Using the Row number in the error message, check the Generic Index file to determine which field the error relates to. Then, using the IBM CMOD Administrator Client to update the date format to match the format of the data itself. In the case of this example, remove the dash ("-") characters from the date format string, and attempt the load again.

			Also, check the Application definition, under Load Parameters - select the date field that is causing problems, and check the date field parameters -- ensure there are no spaces or tab characters ''before'' or ''after'' the date field specification (like %m/%d/%Y). As a reminder, the 'Character Removal' fields only remove characters from the INPUT fields, not the date field specification itself!

	== Articles Related to this message ==		== Articles Related to this message ==

Jderrick: Added a description of the issue in the example.

2021-09-29T02:31:37Z

Added a description of the issue in the example.

← Older revision		Revision as of 02:31, 29 September 2021
Line 20:		Line 20:
	== What happened? ==		== What happened? ==
	The date format that was inside the file didn't match the date format that was expected by CMOD, in the Application configuration.		The date format that was inside the file didn't match the date format that was expected by CMOD, in the Application configuration.

			In the example above, CMOD was expecting dashes between the year and month and day of the month. In order for OnDemand to be able to properly parse the date, it must match the format defined in the Application.

	== Troubleshooting ==		== Troubleshooting ==

Jderrick: Fixed link to arsload.

2021-09-29T02:29:16Z

Fixed link to arsload.

← Older revision		Revision as of 02:29, 29 September 2021
Line 16:		Line 16:

	== What were you doing? ==		== What were you doing? ==
	You were trying to load data into CMOD using [arsload], possibly for the first time since the Application Group or Application was configured.		You were trying to load data into CMOD using [[arsload]], possibly for the first time since the Application Group or Application was configured.

	== What happened? ==		== What happened? ==

Jderrick: Added link to IBM CMOD Date formats

2020-01-24T21:39:28Z

Added link to IBM CMOD Date formats

← Older revision		Revision as of 21:39, 24 January 2020
Line 26:		Line 26:
	== Articles Related to this message ==		== Articles Related to this message ==
	[http://www.odusergroup.org/forums/index.php?topic=1906.0 OnDemand User Group Forums Post]		[http://www.odusergroup.org/forums/index.php?topic=1906.0 OnDemand User Group Forums Post]

			[[Date and Time formats in Content Manager OnDemand]]

Jderrick: Initial edit of ARS1129E.

2020-01-24T00:32:49Z

Initial edit of ARS1129E.

New page

{{TOCright}}
== What was the error? ==
'''Message Number''': 1129

'''Message Severity''': Error (Corrective action is required to continue)

'''Message Name''': ARS1129E

'''Message Text''': Row X: The string "20190125" could not be converted to a date from the format of %Y-%m-%d

== Example ==
ARS1129E Row 1: The string "20190125" could not be converted to a date from the format of %Y-%m-%d

== Related Errors ==
[[ARS1315W|ARS1315W Warning: The date string "20190125" with date format "%Y%m%d" does not match a specific date.]]

== What were you doing? ==
You were trying to load data into CMOD using [arsload], possibly for the first time since the Application Group or Application was configured.

== What happened? ==
The date format that was inside the file didn't match the date format that was expected by CMOD, in the Application configuration.

== Troubleshooting ==
Using the Row number in the error message, check the Generic Index file to determine which field the error relates to. Then, using the IBM CMOD Administrator Client to update the date format to match the format of the data itself. In the case of this example, remove the dash ("-") characters from the date format string, and attempt the load again.

== Articles Related to this message ==
[http://www.odusergroup.org/forums/index.php?topic=1906.0 OnDemand User Group Forums Post]