ARS1130E - Revision history

Jderrick: Minor changes.

2021-09-29T02:19:25Z

Minor changes.

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

	== What happened? ==		== What happened? ==
	~~You were trying to load information into CMOD~~, ~~and~~ the indexer couldn't find data for each of the defined fields. Content Manager OnDemand doesn't permit fields to be left empty, so the load failed.		During the arsload process, the indexer couldn't find data for each of the defined fields. Content Manager OnDemand doesn't permit fields to be left empty, so the load failed.

	== Troubleshooting ==		== Troubleshooting ==
	~~Determine~~ which field is missing. Open ~~any~~ index file that may have been delivered with the documents, or for an index file that was created by the ACIF, PDF, or OS/390 indexer. Review the list of fields that appear in the index file, and compare them against the list of fields for the Application Group. Pay special attention to spelling or symbols (CUSTNUM vs. CUST_NUM).		First, determine which field is missing. Open the index file that may have been delivered with the documents, or for an index file that was created by the ACIF, PDF, or OS/390 indexer. Review the list of fields that appear in the index file, and compare them against the list of fields for the Application Group. Pay special attention to spelling or symbols (CUSTNUM vs. CUST_NUM).

	~~Check~~ with the team that generated the file - have they made changes to the file or indexes that caused this problem?		Then, check with the team that generated the file - have they made changes to the file or indexes that caused this problem? If you can identify the missing field, provide it to the team responsible for generating the files.

	If at all possible, have the source system generate a string to indicate that a field is blank, rather than leaving it blank -- for example, include "Not Applicable" or "No Data" or simply a dash character ( - ) to indicate that there isn't any information in that field. A blank field may confuse end users and ~~lead them~~ to ~~believe~~ data is missing or was deleted.		If at all possible, have the source system generate a string to indicate that a field is blank, rather than leaving it blank -- for example, include "Not Applicable" or "No Data" or simply a dash character ( - ) to indicate that there isn't any information in that field. A blank field may confuse end users and make documents more difficult to find - often resulting in people assuming the data is missing, or was deleted.

	In cases where it's not possible to modify the upstream system, you can insert a default value with the CMOD Admin Client, in the Application definition window, under the Load Information tab. See the example here:		In cases where it's not possible to modify the upstream system, you can insert a default value with the CMOD Admin Client, in the Application definition window, under the Load Information tab. See the example here:

Jderrick: Added CMOD Application Default Value graphic.

2021-01-29T15:14:48Z

Added CMOD Application Default Value graphic.

← Older revision		Revision as of 15:14, 29 January 2021
Line 28:		Line 28:
	If at all possible, have the source system generate a string to indicate that a field is blank, rather than leaving it blank -- for example, include "Not Applicable" or "No Data" or simply a dash character ( - ) to indicate that there isn't any information in that field. A blank field may confuse end users and lead them to believe data is missing or was deleted.		If at all possible, have the source system generate a string to indicate that a field is blank, rather than leaving it blank -- for example, include "Not Applicable" or "No Data" or simply a dash character ( - ) to indicate that there isn't any information in that field. A blank field may confuse end users and lead them to believe data is missing or was deleted.

	In cases where it's not possible to modify the upstream system, you can insert a default value with the CMOD Admin Client, in the Application definition window, under the Load Information tab.		In cases where it's not possible to modify the upstream system, you can insert a default value with the CMOD Admin Client, in the Application definition window, under the Load Information tab. See the example here:

			[[File:SettingADefaultValue.png\|720px]]

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

Jderrick: /* Articles Related to this message */

2021-01-29T15:13:28Z

Articles Related to this message

← Older revision		Revision as of 15:13, 29 January 2021
Line 31:		Line 31:

	== Articles Related to this message ==		== Articles Related to this message ==
			[[Default Values and the Generic Indexer]]

	[http://www.odusergroup.org/forums/index.php?topic=3060.msg12221#msg12221 OnDemand User Group - Enhancement Request Forum] (Registration required.)		[http://www.odusergroup.org/forums/index.php?topic=3060.msg12221#msg12221 OnDemand User Group - Enhancement Request Forum] (Registration required.)

Jderrick: Initial edit for ARS1130E.

2021-01-29T15:11:55Z

Initial edit for ARS1130E.

New page

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

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

'''Message Name''': ARS1130E

'''Message Text''': X fields submitted by the indexer, Y expected

== Example ==
ARS1130E 7 fields submitted by the indexer, 8 expected

== Related Errors ==
ARS4311E Loading failed

== What were you doing? ==
Loading data into Content Manager OnDemand with arsload.

== What happened? ==
You were trying to load information into CMOD, and the indexer couldn't find data for each of the defined fields. Content Manager OnDemand doesn't permit fields to be left empty, so the load failed.

== Troubleshooting ==
Determine which field is missing. Open any index file that may have been delivered with the documents, or for an index file that was created by the ACIF, PDF, or OS/390 indexer. Review the list of fields that appear in the index file, and compare them against the list of fields for the Application Group. Pay special attention to spelling or symbols (CUSTNUM vs. CUST_NUM).

Check with the team that generated the file - have they made changes to the file or indexes that caused this problem?

If at all possible, have the source system generate a string to indicate that a field is blank, rather than leaving it blank -- for example, include "Not Applicable" or "No Data" or simply a dash character ( - ) to indicate that there isn't any information in that field. A blank field may confuse end users and lead them to believe data is missing or was deleted.

In cases where it's not possible to modify the upstream system, you can insert a default value with the CMOD Admin Client, in the Application definition window, under the Load Information tab.

== Articles Related to this message ==
[http://www.odusergroup.org/forums/index.php?topic=3060.msg12221#msg12221 OnDemand User Group - Enhancement Request Forum] (Registration required.)