Overview

This article will detail common Input Template (Planning Template) error messages and how to resolve them 

This article is broken down into sections for the following error messages

1. An error occurred while saving data. Couldn't Store all Entries

2. Storing Failed. Cannot insert the value NULL into column

3. Storing Failed. The merge statement conflicted with the Foreign Key...

4. Storing failed. The merge statement attempted to update or delete the same row more than once

5. CreatedBy, UpdatedBy, CreatedOn, UpdatedOn are not getting updated

An error occurred while saving data. Couldn't Store all Entries

There are a couple reasons for this error. 

1. Make sure that all dimension being stored back in this template exists in their respective dimensions. 
2. Make sure that your budget settings are unique enough. 

If #1 above checks out, typically this error means that your budgeting settings are not detailed enough and our save data routine is not finding unique enough transactions. For example, below is a diagram of a potential setup in the CorpDemo

 

• Row 2 already exists in your database
• Row 3 gets added via a budget template, your budget template is not storing to currency
• Row 3 successfully saved the first time because its a unique transaction (not storing to currency)
• When you attempt to store again, it fails. This is because without currency, the application does not know whether to update row 2 or row 3. 

Resolution:

Review your budget settings and make sure they include all dimensions that is relevant to existing data in your Module. These dimensions need to be in the mandatory fields section. 

Storing Failed. Cannot insert the value NULL into column

Users will receive this error message because a value they are storing does not exist in the respective dimension. Certain modules have required dimensions. As an example, the General Ledger module has Account, Entity, Scenario and TimePeriod as mandatory dimensions. If in your budget template, you provide an account code that does not exist in your Account dimension, users will receive this error. 

Resolution:

Ensure that all dimension codes being stored back in the template are valid and exist in its respective dimension.

Storing Failed. The merge statement conflicted with the Foreign Key...

Similar to the above, users are getting this error message because a value being stored back does not exist for a mandatory dimension. 

Resolution:

Ensure that all dimension codes being stored back in the template are valid and exist in its respective dimension.

Storing failed. The merge statement attempted to update or delete the same row more than once

Users will receive this error message due to their input template having the same data twice. 

Resolution:

1. Ensure all dimension codes being stored back in the template exist in their respective dimension. 
2. Review your input template to make sure that no duplicates are being stored. A duplicate is determined by those dimensions that are part of the mandatory dimensions in your budget settings. 

CreatedBy, UpdatedBy, CreatedOn, UpdatedOn Are Not Getting Updated

By default, the application will add information about who created/updated a transaction and when.

Resolution:

If these fields do not appear updated in your SolverDW database, update your integration package to the latest version.