Attention: Missing Dimension Codes – Starting with the June 2023 release, module integrations will no longer accept missing dimension codes. Instead, the integration process will fail and report the missing dimensions to the event log. Cases where the dimension code is blank will continue to function as before. This change specifically applies to dimension codes that exist in the source data for the module, but do not exist in the dimension members.
To remedy the errors associated with missing dimension codes, simply add the dimension codes to the Data Warehouse dimension and re-run the integration or job. The integrations used to import dimension codes should also be reviewed and updated to avoid future errors with importing data.
Happy June Solver users! This update will focus on the Data Warehouse with some changes that you should be aware of to the user interface on the Jobs page as well as some great fixes to your email notifications to ensure that you receive the best and most up-to-date information about your data. The June Solver update also includes huge improvements to error messaging and tooltips for the Data Warehouse that we think users will find very helpful when creating integrations. Reminder for all users, Beginning this month, event log history will be shortened to the past 30 days only. Please get in touch with Solver Support with any questions.
06/27/23: Due to the volume of validation errors that we have seen following our June release, we will allow users to run integrations with missing dimension codes to ensure that your Jobs will continue running and give our users time to correct the underlying data validation issues. We are also seeing a small number of errors when writing duplicates to the GL detail which does technically allow duplicate rows. Due to this, we have made it so data validation of duplicate rows will no longer apply to the GL detail table.
We will update users on any changes that need to be made following these updates. Please contact support (support.solverglobal.com) with any questions about your implementations.
New Features
Data Warehouse
- Added improved error messages in cases of data insert errors when creating an integration. (Pictured Below)
This includes improvements to SQL error messages for:- Duplicate Data
- Missing Dimension Codes
- Duplicate Dimension Codes
- Added improvements to tooltips on Integrations, Rules, and Jobs.
- Added the ability for columns in task mapping preview to automatically expand for improved visibility.
- Changes have been made to the process of scheduling a Job:
- Corrected the “Create and Run” button to Create when saving a Job.
- Changed the same button to “Update” when editing a Job.
- Removed the ability to automatically run a job once it has been created.
- Added the ability for BCv2 connector users to retry request attempts if they get a notification that the request was canceled or aborted.
- Fixes an issue where, as a user tabs to the next box they will receive an error and will be unable to save the dimension code.
Bug Fixes
Reporting
- Fixes an issue where the file users receive from Publisher, contained an extra underscore at the end of the file name.
Data Warehouse
- Fixes an issue where the select all button on the Data Explorer page would not unselect after deleting all of the transactions on the table.
- Fixes an issue where Data Validation of duplicate rows was not applying to the GL detail table.
- Fixes an issue on the Monthly Rates table when deleting a value in the table and turning on Effective Rates then the values would round down (1.000, 2.000, etc) instead of using the exact last rate (1.232453).
- Corrected the DocumentNumber mapping when using QuickStart for Business Central, Accounts Payable integrations.
- When creating a dimension the Alias attribute’s label showed it allowed 200 characters, the field only allows 50 characters.
- Fixes an issue where some users were receiving Job notification emails that only contain a subject and were missing a body while, Some email notifications would also have a subject alerting the user to a failed job when the job had run successfully.
- Removed reference to “No User Specified” on Jobs screen.
Before
After - Fixes the following issues with QuickStart for Intacct:
- Update Budget integration mapping Department to Dept_NO.
- STAT accounts should always equal zero.
- Update Budget integrations to multiple by the natural account balance.
- Fixes an issue where QuickStart for Intacct did not complete successfully.
- The filter “Currency Type” has been changed to “Currency” on the Monthly Rates menu.
Administration
- Fixes an issue where notification banners were not properly displaying special characters.
- Fixes an issue where the number of selected companies being displayed under the licensing screen was incorrect.