There will always be some errors relating to how data is mapped into Details. We'll get most of it right, but errors are bound to happen. Check out the table below for an explanation of what each error is and how to fix it!
In the table below are all possible error messages. The 'Description' column will let you know what the problem was, and the 'Action' columns tells you what needs to be done to resolve it.
It's important to note that some of these are critical errors, and some are more like notifications. For example, a payment not being logged is a problem that requires action, but an item being matched to an existing Details item requires little to no action. Pay close attention to the icons associated with each error.
- Red icons are for critical errors.
- Orange icons are for medium-level issues that you should review.
- Yellow icons are for low-level, low-impact issues that may not necessarily require action on your part.
|Client - No Event||Client won't show on event list because they have no events in this import.||You should manually create this client.|
|Event Totals||Event totals may be incorrect.||Manually confirm totals.|
|Event Creation||Empty client record was created because no client could be found for event in import.||Add any missing contact information to the created client record.|
|Event Date||Event date is formatted improperly and could not be read.||Set the event date manually.|
|Event Collision||Two or more events exist with the same name for the same client. All related events may have issues.||Check all related events for accuracy.|
|Item Match||Imported item was matched to existing item.||Check item details for accuracy.|
|Event Payment||Payment was not logged because there was no 'Receipt Amount'||Manually enter the payment, if necessary.|
|Event Payment - No Client/Event||Payment was not logged because no matching event and/or client could be found.||Manually enter the payment, if necessary|
|Event Total Paid||The total amount paid does not match the sum of payments logged.||Manually adjust logged payments, if necessary.|
|Arrangement Client/Event||Arrangement was not created because no matching event and/or client could be found.||Manually enter the line item, if necessary.|
|Worksheet Line Item Conflict||There is more than one line item in the same worksheet group with the same name. Only one will be added and item ingredients for both will be combined.||Manually create a new line item and split the ingredients, if necessary.|
|Worksheet Client/Event||Item was not added to a worksheet because no matching event and/or client could be found.||Manually create event and add line items, if necessary.|
|Worksheet Group Created||The worksheet group was not listed in the Event Agreements file, but was created anyways.||Verify group line items for accuracy.|
|Event Worksheet Item Cost||The associated item had a different cost on the same event (i.e. the same bloom has two different costs within the same event).||Verify the item cost on the associated worksheet.|
|Fees Discounts Client/Event||Fee(s) and/or discount(s) not added to a worksheet because no matching event and/or client could be found.||Manually add fee(s)/discount(s), if necessary.|
|Payment Description||The imported payment description was too long.||Review payment description.|
|Event Missing Item||The item was not in the item library import.||Manually create the item, then add the item to the associated worksheet line item.|
|Worksheet Line Item Created||The line item was not listed in the Event Agreements file, but was created anyways.||Verify line item components for accuracy.|
If you have any questions, or need assistance, please contact Details Support at firstname.lastname@example.org or by phone at (386)255-9594 - we're here to help!