iDMS Release Notes

The following release notes describe the new features, enhancements, and bug fixes deployed to iDMS, grouped by year and listed by release version.

Latest Release: iDMS 1.39 — August 2026

The following new features and enhancements are available in the August 2026 release.

Importing US legislative districts

Three new address fields are available when mapping addresses in iImport and iUpdate: US Congress, State Senate, and State House.

Previously, iMIS populated these districts only when a staff member edited an address manually in the iMIS web pages, because the lookup runs against an external address-verification service that iMIS calls only from its own screens. That meant districts could not be populated in bulk. Organizations can now source the values themselves — the free US Census Geocoder is the usual source — and import them like any other address field.

See Address guide for information.

Key capabilities:

Map US Congress, State Senate, and/or State House under the Address Details source group, on both new and existing contacts.
Column headers matching the field names are mapped automatically.
Values are limited to five characters. Longer values are truncated to the first five characters and reported as a warning; the contact still imports rather than being rejected by iMIS.
New per-row warnings identify when iMIS has silently discarded a congressional district, either because the Automatically set congressional district based on address (US only) setting is disabled, or because the imported address purpose does not match the Address to use for congress setting.

⚠️
Important
Only US Congress is gated by the two iMIS settings above. State Senate and State House always save regardless of iMIS configuration. Values should be the district number alone (10, 25), not TX-21 or District 21, to match how iMIS stores the value from its own lookup.

Batch Number on Generate Renewals

A new optional Batch Number field is available on the Generate Renewals mapping, between Bill Date and Effective Date. Renewal invoices are posted into the batch specified instead of one iMIS creates on its own, which allows finance staff to route a renewal run into a batch they have already set up for reconciliation.

iMIS accepts a supplied batch only when billing a single contact. On a mass billing run it ignores the batch and creates its own without reporting it. iDMS now rejects those combinations at the mapping-validation step — before any invoices are generated — and explains why, rather than allowing the run to succeed while billing into an unexpected batch.

See Generate Renewals Guide for information.

Key capabilities:

Batch Number can be used with Only Bill Individual iMIS ID, or with an iMIS ID mapped on the import itself. In the latter case the import data must contain only one row, because no Only Bill contact was given.
Batch Number cannot be used with Only Bill Contacts From Query Path or Only Bill Contacts In Chapter Code — billing from a query or chapter always creates a new batch in iMIS.
The batch must already exist in iMIS, must be Open (a batch set to Ready or already posted is rejected), and must be dated the same day as the Bill Date. When Bill Date is not mapped, the bill date is today, so the batch must be dated today.
Batch numbers are limited to 10 characters.
Seven new validation messages identify each failure condition up front, replacing a mid-run iMIS failure or a silent misfile.

Existing renewal mappings are unaffected. The field is optional and unmapped by default, so iMIS continues to select the batch exactly as before. No customer action is required.

Clearing a file upload field with ERASE

Panel fields of type File upload can now be cleared through iImport and iUpdate. Entering ERASE in the File URL mapping — instead of a URL — removes the existing document from iMIS rather than downloading a new one. Previously the only way to remove a document was to open each contact in iMIS and delete the file by hand.

Nothing new appears on the mapping screen; the keyword is simply understood where a URL was previously required. It also works per row, so a single spreadsheet can attach a document to one record and clear the document on the next.

See Delete Action guides for information.

Key capabilities:

Type ERASE directly into File URL to clear the field on every record in the import, or map File URL to a column and enter ERASE in the cells of the rows to be cleared.
Matching is case-insensitive and surrounding spaces are ignored. The whole cell must be the keyword — a real URL that merely contains the word (for example http://host/clear.pdf) still downloads normally.
On an existing record, the document is removed and the rest of the row imports normally. On a new record, the record is created with no document and iDMS notes there was nothing to erase.
Any blank-out text configured under Cells containing the following text will be blanked out clears the file as well.

⚠️
Warning
DELETE, EMPTY, BLANK, CLEAR, NONE, and NULL also clear the field. Do not use any of them in a spreadsheet as a placeholder meaning "leave this record alone" — they will remove the document. N/A is safe; NONE is not.

Fixes

File Content Type and File Type are now applied. Previously, the File Content Type (Optional) and File Type (Optional) values were collected and saved but never used. iDMS now determines the content type and file type from the downloaded file itself, and falls back to these two mapped values only when the download does not identify the file. They are ignored entirely when clearing a field.
Spaces around a File URL are now trimmed. Previously, a cell containing a leading or trailing space produced a malformed address and the row failed. Surrounding whitespace is now removed before the download is attempted.
ERASE now takes precedence over Ignore Blank Values. Previously, having Ignore Blank Values in File enabled could quietly cancel an erase. An explicit erase keyword is now always honored.
Renewal batch problems are now caught before billing. Previously, an invalid batch on a Generate Renewals run either failed part-way through with the iMIS message "You must select an open batch whose effective date matches the billing run date", or succeeded while billing into a batch iMIS created on its own. These conditions are now detected at validation, before any invoices are generated.

Previous Releases

iDMS Release Notes 2026

iDMS 1.35.0 — April 2026

Fixes

Program items added via iDMS could not be edited or saved in iMIS. Previously, program items created through iDMS could not be edited or saved in iMIS when registration options were already present, due to missing records that iMIS requires to process updates. All necessary records are now created and linked during the event creation and update process, so program items can be edited and saved in iMIS regardless of whether registration options already exist.
Applying an open credit larger than the invoice total caused an error. Previously, using an open credit to pay an invoice where the available credit exceeded the invoice total produced an error, because the system expected the credit amount to match or be less than the invoice balance. Only the amount needed to cover the invoice is now applied from the available open credit, even when more credit is available.
Custom panel sources are now checked for iDMS access. When an iDMS import references a custom panel source, new validation checks confirm that the proper access permissions are set. If they are not, the import is blocked and an error message explains which permissions are missing. This message may appear on the mapping or validation pages. See Granting iDMS access to IQA queries and panel sources.
iUpdate filter labels now use the value defined in the query Search Label field. Filter labels throughout iUpdate now display the IQA query filter Search Label rather than the raw internal property name, making filters easier to identify when reviewing or setting up iUpdate jobs.

iDMS 1.34.0 — March 2026

The iDMS 1.34 release includes updates and enhancements to iImport and iUpdate Cloud.

Reversing invoices using iDMS

Dues invoices (cash, persisted cash, and accrual) and order invoices can now be reversed in bulk using iImport and iUpdate. This allows system administrators to correct invoicing errors or update incorrect charges without reversing each invoice manually. The reversal mappings are configurable, so organizations can define how different types of reversals are processed.

Key capabilities:

Dedicated mapping sections for Accrual Reversal, Cash Reversal, and Order Reversal that enable you to reverse dues and order invoices.
Reversal-specific fields, such as Invoice Ref Num, Adjustment Date, and Adjustment Reason, that allow you to define how invoice reversals are processed.

Key use cases:

Reversing a batch of invoices created accidentally due to incorrect billing rules, pricing updates, or product configurations.
Cleaning up test data by removing test invoices or duplicates created during initial configuration, testing, or integrations.
Managing order-related reversals while capturing adjustment details for reporting and auditing.

From the Cloud Dashboard, choose either iImport or iUpdate. In the mappings section, select the Invoice Reversal source. The mapping interface then displays the fields required for Accrual Reversal, Cash Reversal, or Order Reversal, so they can be mapped as needed.

Overriding shipping and handling amounts

When inserting orders in iDMS iUpdate or iImport, you can override the shipping and handling amounts by entering values in the Overridden Shipping Amount or Overridden Handling Amount fields. When these fields are populated, the specified amounts replace the default iMIS shipping and handling values for orders created in iMIS EMS.

Fixes

Canceled iDMS job logs page stuck in a loading state. Previously, when a job was canceled in iDMS, the job logs page could remain stuck in a loading state and display no information, even though the job showed as canceled in the dashboard. The logs page now correctly recognizes canceled jobs and updates based on the job's actual status.
Program item Additional Information field not consistently saved. When a program item was added or updated through iDMS property mapping, the Additional Information field did not always retain information when the program item was viewed in iMIS. The field is now correctly assigned and saved, so any provided information is preserved during the update process.
The Display to staff users only setting for registration options and program items. When registration options and program items were imported or updated through iDMS, the Display to staff users only setting was automatically enabled, which could result in inconsistent event visibility. The setting is no longer enabled by default, so imported items are visible to all users. Existing registration options and program items are not affected by this change.
Event function Category field now correctly accepts comma-separated values. Previously, entering comma-separated values in the Category field for program items or registration options could produce unexpected results, causing categories to be assigned incorrectly or inconsistently. The Category field now behaves predictably regardless of how values are entered.
Relationship Begin and End date fields not handled correctly when left blank. Previously, entering NULL or leaving the Begin and End dates for relationships blank meant iMIS did not always process the information as expected. These requests are now handled correctly, allowing relationships to be created or updated successfully when date values are not provided.
Clearing the billing product Deferred Income and Income account fields using blank values. Previously, using iDMS to clear the Deferred Income or Income account fields on iMIS billing products left the fields unchanged even when the job was configured correctly, because iDMS attempted to look up a GL account using the blank value and skipped the update when no match was found. Providing a blank value for either field now clears it in iMIS as intended.
Character limit removed from the Membership Group Name field. Previously, the Membership Group Name field in the iDMS Products source was limited to 36 characters, causing validation failures when longer names were entered, even though iMIS has no such restriction. This limitation has been removed and the field now accepts values of any length.
Events source — required field indicators added for Registration Option and Program Item codes. The Registration Option Code and Program Item Code fields in the Events source are required when working with their corresponding items, but this was not clearly communicated in the interface. A visual indicator now appears next to these fields to make their required status immediately apparent, reducing validation errors during setup.

iDMS Release Notes 2025

iDMS 1.32 — November 2025

New features

Added the ability to insert new subscriptions on existing invoices using the Associated Invoice ID field in the Subscriptions source.
When inserting subscriptions, records are no longer billed unless specified with the Bill Subscription field in the Subscriptions source.
Added a new Event Operation source, which can be used to close, cancel, or delete iMIS events.
Added a Source Type dropdown to Task History in the Dashboard, providing additional search filters.
Warning messages now appear when importing a task or template that already exists in the environment.
When downloading the report from a job's logs, the Excel file now includes an additional tab with more information about the job, such as Cloud ID and Job Number.

Fixes

When inserting inventory receipts, the iMIS product's total cost is now adjusted as expected.
Added the Charitable Item field for event registration options, program items, and cancellation fees. It is now possible to set this field and keep the Fair Market Value at 0.
iDMS now honors the Automatically set chapter based on zip code setting in iMIS. A new Assign Chapter by Zip Code field has also been added to the Address Details source for overwriting a record's existing chapter subscription.
Added a Quantity field to the Event Registrations source to control how many times a registrant can purchase a program item when registering for an event. This was not previously possible.
In the Committee Codes source, the description code now displays as required (*).

iDMS 1.31 — July 2025 (7/9/2025)

New features

Added the ability to export and import tasks in bulk between different Cloud IDs.
Added the ability to post batches — you can now set a batch to ready or open, or perform the post operation. This is useful when a merchant closes out the day at 10 PM.
Added the ability to delete promotions as part of the Delete action.
Added the ability to apply payments based on the Invoice ID field, which is useful for cash dues.
Added clearer indication of read-only fields in panels. iDMS now warns when a mapping targets a read-only field.
Added the ability to update social profiles through the new Social Profile source.
Redesigned the action buttons. The action name has moved to the top of the button to fit smaller laptop screens, and the "when to use" wording has been improved.
Added the ability to update gift items when the description is missing, working around an existing API bug that previously required a gift description.
Added error logging when the import source contains duplicate headers.

iDMS 1.30 — June 2025 (6/2/2025)

Hotfixes

June 4, 2025 (v1.30.2) — Fixed an issue where importing a gift in iMIS 2017 caused the batch date to override the Gift Date. If a Gift Date is specified, that date is now used on import.
June 4, 2025 (v1.30.2) — Added support for a new panel type, Invoice. This panel type was recently added to iMIS and can now be referenced within the iDMS source.

New features

Added Create Auto Match, which allows source columns in a new iImport or iUpdate job to match automatically based on the columns in your spreadsheet or IQA.
Added the ability to pull data logs from a job run when the job reports "Skipped due to multiple records (2) matched!" or "No contact record found". New Warnings and Warning Data tabs are now available.
Added data validation support for other cultures. Date formats of mm/dd/yyyy or dd/mm/yyyy are handled, as long as the date format is set on the incoming import (Excel spreadsheet) or IQA.
When loading a template for use within an import, the Select button has moved to the left side of the screen, alongside the eyeball link used to identify the mapping.
When importing to the Committee Codes source, you can now import Group and Notes.

Fixes

When importing billing products, the Type is no longer included on a product code if it already exists within the import.
Fixed a warning message when creating an iSchedule task that incorrectly read "The tasks will not run unless scheduled of manually run".
The Program Item Name field length has been adjusted to 120 characters when using the Event Setup source.

iDMS 1.29 — April 2025 (4/29/2025)

New features

Added a details description field to the Gift source, allowing users to enter gift details.

Fixes

Fixed an issue where duplicate reservations were not checked when importing event registrations, which allowed a second registration to be imported.
The Relationship source previously required only ID. It now requires ID, Relationship Type, and Target iMIS ID.
Fixed an issue where an iSchedule scheduled job could continue to run after the end of a client's subscription.
Fixed an issue where importing a registration could use a prior open batch date as the transaction date instead of the date in the import.
Fixed an issue where state and country fields could not be cleared. These fields can now be cleared.
Fixed an issue where template mappings did not load correctly using Insert with Matching, causing all fields to default to match on.
Increased Event Title in the Event source to 120 characters.
Fixed an issue where committees could not be updated using Insert/Update.
Fixed an issue where the work phone always flowed down to a new individual record when flowdown was disabled.

iDMS 1.28 — January 2025 (1/29/2025)

Hotfixes

February 10, 2025 (v1.28.1) — Fixed an issue where a user could not import an event registration for a member who did not have an existing payment object in iMIS, producing the error "no payment information is available".
March 10, 2025 (v1.28.2) — Fixed an issue where a user might periodically receive the error "iMIS version "" cannot be validated for Cloud ID".
March 10, 2025 (v1.28.2) — Fixed an issue where switching between Contact Details and csContact Panel Data did not work.

New features

Added the ability to create an event registration option with support for Taxable GST and/or Taxable PST.
Added the ability to create and update products with support for Taxable GST/HST and/or Taxable PST.
Improved job failure notifications — the Cloud ID is now visible in the subject line.
Event registrations now support including the default program option.
The iMIS REST API now handles validation for email addresses.
The flowdown feature in iMIS can now be overridden in iDMS, without turning it off in the iMIS settings.

Fixes

Fixed an issue preventing the deletion of GL account codes that include decimals.
Fixed an issue on a brand new database that produced the error "Currency date cannot be found".
Fixed an issue where removing ORG or ORG ID from a member blanked out the Title field.
Fixed an issue where a new event could be imported with an end date earlier than the start date.
Fixed an issue when removing the Chapter Admin role from a member without removing them from the chapter.

iDMS Release Notes 2024

iDMS 1.27 — November 2024 (11/20/2024)

Hotfixes

December 9, 2024 (v1.27.1) — Fixed an issue where a user could not update an Order source.

New features

Import and update freight rates. Added the ability to import freight rate files, matching the behavior of the Freight Rate Importer.
Clearer REST API errors. When an error occurs, the message now identifies what it relates to, and indicates when the user should contact ASI.
Template changes. When a template has match-on fields because it was used for an Update action, and you want to use it for Insert, iDMS now ignores the match-on setting for those fields.
Orders are now allowed for Update actions.
IQA warning. A warning now appears when a selected IQA does not have Available via the REST API checked on the Security tab.

Fixes

Fixed an issue where forward slashes were not allowed in email addresses.

iDMS 1.26 — September 2024 (9/30/2024)

Hotfixes

October 8, 2024 (v1.26.1) — Fixed an issue where a user could not update a template directly after creating it.
October 10, 2024 (v1.26.2) — Fixed an issue in Promotions where a new item could not be inserted on an existing promotion.
October 10, 2024 (v1.26.2) — Fixed an issue in Relationships where using Insert/Update could return an "Updated" message when no update occurred.

New features

Import and update promotions. Added the ability to import promotional coupons for use in the checkout process.
Update an order status. Order statuses can now be changed with iDMS.
Re-enable iSchedule jobs if they are disabled and the iWorkflow role is enabled.
Edit and update events.
Set the purchase order when importing orders.
Improved UI for downloading records from the import history.

Fixes

Fixed an issue where row and column data exceeded the capacity to download.
Fixed an issue where inserting into a single-instance panel failed when an amount or currency value was zero.
Fixed an issue where using Insert with Matching for a panel locked the Match On setting on the second matched-on field.

iDMS 1.25 — June 2024 (6/26/2024)

Hotfixes

July 3, 2024 (v1.25.1) — Fixed an issue where iDMS could run multiple times when validation took too long.
July 3, 2024 (v1.25.1) — Fixed an issue where inserting a member into a chapter with an ampersand (&) in the name caused a REST API error.
July 10, 2024 (v1.25.2) — Fixed an issue where iDMS did not display parent-type Event panel sources.
July 17, 2024 (v1.25.3) — Fixed an issue where the Accounting Financial Entity option did not persist in Event Registration.
July 24, 2024 (v1.25.4) — Fixed an issue where a new release of EMS caused an error when selecting or browsing an IQA with parameters.
August 21, 2024 (v1.25.5) — Fixed an email validation issue causing the error "Sequence contains more than one matching element".
September 5, 2024 (v1.25.8) — Fixed an issue with Events validation.
September 10, 2024 (v1.25.9) — Fixed an issue to support duplicate parameter names.

New features

Added Transaction Date to the Event Registrations source, allowing a transaction date to be used when importing a registration that did not occur on the current date.
Added Entity Code (Name.ORG_CODE) to the Contact Details source. Available starting with the .180 release of EMS.
Licensing and UI changes to support the new Workflow enhancement for iDMS.
Numeric defaults. If a spreadsheet column is blank and the mapped field is numeric, the update or insert now defaults to zero.
Internal performance improvements to speed the loading of user-defined tables, panel definitions, and fields.

Fixes

Fixed an issue where a record could not be inserted into an empty panel with just an iMIS ID.
Fixed an issue where "No Match Found" when updating a business object did not display the iMIS ID.
Fixed an issue where a webhook could not be called if the scheduled job was already in progress.
Fixed an issue where inserting a new group member and role failed to find the role, because only one group type was returned in the search.

iDMS 1.24 — May 2024 (5/16/2024)

Hotfixes

May 17, 2024 (v1.24.1) — Fixed a permission issue after trigger endpoints.
May 17, 2024 (v1.24.1) — Fixed an issue where Source Code was not set on pledges.
May 22, 2024 (v1.24.2) — Fixed performance issues in the validation setup step.
May 22, 2024 (v1.24.2) — Query filter values are now shown in logs.
May 22, 2024 (v1.24.2) — Fixed an issue where the ID property was missing or empty in a business object.

New features

Added user-defined fields to Event Import, supporting MUF_1 through MUF_10.
More information in stack traces. Include stack trace details when reporting issues to CSI.
Allow Insert into CsNameNote using fields other than ID for Match On. The Insert with Matching action allows you to insert into CsNameNote and no longer requires the ID.
More information when updating business objects and panels, including the iMIS ID.
Warning when loading or using a template. If the spreadsheet or IQA columns do not match the selected template, a warning appears, but you can continue.
Support for Source Code when inserting pledges. This field was previously unavailable.
New label for the Insert button, clarifying that Insert can be used for inserting into tables such as Product and Gen Tables.

Fixes

Fixed an issue where iDMS ignored the Order Date in the file and incorrectly created a new batch when a batch with that date already existed.
Fixed an issue where an IQA did not appear immediately in iDMS after being created in the staff site.
Fixed an issue where performing an Insert/Update and matching on Organization Name did not recognize an existing record and created a new one.
Fixed an issue where panel names were not listed in alphabetical order.

iDMS 1.23 — February 2024 (2/20/2024)

Hotfixes

February 21, 2024 (v1.23.1) — Fixed an issue where deleting an activity by sequence or business object also deleted committees.
February 22, 2024 (v1.23.2) — Fixed an issue with Insert/Update where panels were not updated or inserted.
February 26, 2024 (v1.23.3) — Fixed an issue with orders where the last line item was duplicated.

New features

Import Event Setup data. See the iDMS documentation to learn more.
Set the Order Type when importing orders. Requires EMS version 20.3.166 or later.
New field in the Cart Items source to set number of days. You can now set the number of days for cart items older than a set value in order to delete them.
Changes to default option settings. When changing a global option setting, you can apply the change to existing jobs, existing templates, or neither.
Quickly toggle between the Contact Details and Panel Data (CsContact) sources. A link next to the sort button takes you to the alternate contact data.

Fixes

When the mapping for an Update action contains only Match On fields and no fields to update, the task is now prevented from running.
Fixed an issue where Insert with Matching did not correctly insert into panel fields.

iDMS Release Notes 2023

iDMS 1.22 — November 2023 (11/30/2023)

New features

Generate renewals. See the iDMS documentation to learn more.
Update product inventory. See the iDMS documentation to learn more.
Added the ability to delete subscriptions.
Added the ability to update and insert the County field.
Modified the loading message, which now indicates when the task is running.

Fixes

Fixed an issue where users logged into iDMS for an extended period received the error "" is not a valid version" when they returned.
Fixed an issue where Limit the number of results returned in an IQA was not respected by the API endpoint. The value is now honored.
Restricted the creation of an _ORG-ADMIN relationship between two individuals, which is not valid.
Fixed an issue where _ORG-ADMIN in iMIS 2017 was not correctly identified, resulting in a "Not a valid role" error.

iDMS 1.21 — September 2023 (9/26/2023)

New features

Change IDs on multi-instance panels. If information was imported into the wrong person's multi-instance panel, the ID can now be switched or updated to the correct one.
Set the Communication Message Type on the Communication Log source.
Added the IsComplimentary flag to the Subscriptions source mapping.
Append data to multi-select fields. When updating a multi-select field, you can now add a single new choice while all previous values remain unchanged. See the documentation under "Selecting and Mapping a Field."
Validation on email addresses. When importing or updating member email addresses, iDMS now validates that the address is well formed.
Erase dates. Previously, dates such as Birth_Date could not be erased. You can now use the option If text below is found in File, then field in iMIS will be blanked out.

Fixes

Fixed an issue where entering a date while mapping an import saved the date as the previous day.
Fixed an issue where deleting an activity for a member also deleted their cart, if one existed.
Removed the Delete option for panels that combine multiple tables, which caused significant issues: AutoPayInstructionDetail, AutoPayMemberInstructionDetail, CsContact, CsName_Staff, CsNameFin, CsNameNote, FundraisingProfileDonorData, VolunteerAvailability, VolunteerHistory, VolunteerInformation, and VolunteerSkills.

iDMS 1.20 — June 2023 (6/29/2023)

Hotfixes

June 29, 2023 (v1.20.1) — Fixed an issue where the message could falsely report multiple rows affected when Skip update if more than 1 record found was checked.
July 6, 2023 (v1.20.2) — Fixed an output message, and fixed an issue in Groups where system groups were excluded.
August 7, 2023 (v1.20.3) — Fixed an API error when unlocking a user account.

New features

Import orders. iDMS can now import orders. Pay close attention to the Order Grouping field.
Import pledges. Completing the fundraising feature set, you can now import pledges.
Update the attributes on a committee product or group.
Removed CompanyID from CsContact to prevent data corruption.
Adjusted the "Failed" notification to account for partial failures.
Added support for the client time zone on date input.
Enhanced messaging when importing user credentials. User credentials must be created using Insert. The error message shown when attempting an Update has been clarified. Note that unlocking user credentials should still be done using Update.
ID validation checking. iDMS now checks that an ID of "0" is not submitted, which previously caused problems in iMIS.
Health check feature enabled.
Sources redefined and grouped. Sources in iDMS are now grouped into Records Management and Finance, making them easier to find.
Action buttons refreshed. The action buttons have been cleaned up to clarify when to use Insert with Matching versus Insert.
Skip Update if More Than One Record Found now defaults to on.

Fixes

Increased the client timeout to five minutes to allow client endpoints to reconnect and process. Previously, if iDMS waited longer than 100 seconds it returned an error and retried the action later. The error message now indicates that iDMS will retry the insert or update later, so the action is not retried accidentally.
Fixed relationship upsert for iMIS 2017 users.
Fixed an issue where creating a new task could duplicate it, resulting in two tasks pointing to the same import ID.
Fixed an issue where a user-defined table that is also set up as a business object caused iDMS to import it as a business object and error out.
Corrected the "Skipped BO" message, which should read "Created".
Corrected an issue running an IQA with parameters in EMS Professional.

iDMS 1.19 — March 2023 (3/27/2023)

Hotfixes

April 10, 2023 (v1.19.3) — Fixed an issue where updating relationship dates could fail to match because of the GroupMembershipId.
April 14, 2023 (v1.19.4) — Fixed an error when changing the IQA in a scheduled job.
April 14, 2023 (v1.19.4) — Fixed an error when matching on CsContact.ID.
April 14, 2023 (v1.19.4) — Fixed an error where the Relationship source did not match on Type.
May 9, 2023 (v1.19.5) — Fixed an issue with the Relationship source to allow use of Title and date settings.
May 9, 2023 (v1.19.5) — Fixed a cart error on the Delete action.
May 9, 2023 (v1.19.5) — Removed CsContact fields from the source that cannot be set by the API: Member Status, Member Status Date, Member Type Change Date, and Previous Member Type.

New features

Dashboard filtering. Added the ability to drill down into Completed, Failed, and Recurring jobs.
Better guidance for unknown import errors. Step-by-step instructions are now provided.
Enhanced action buttons (Insert, Insert with Matching, Update, Insert/Update, and Delete) for a clearer user experience.
Clear examples for event registration questions and indexes.
General UI and UX enhancements.
Added dates to the Relationship data source: Begin Date, End Date, and Description.
Interactions are now a data source. Add, edit, and delete interactions using the Communication Log data source.
Added the ability to add group members.
Added Chapter Administrator to the Relationship data source, allowing the role to be added, updated, or deleted within the relationship.
Internal database object improvements.
Clearer description when a record is skipped on an Update action and Skip update if more than 1 record found is checked.
IQA renaming is now recognized. Previously, renaming an IQA was not detected because the IQA's unique identifier was saved instead of its name. As a result of this change, IQAs with slashes in the name are no longer supported.

Fixes

Fixed an issue where tasks and jobs canceled with different parameters.
Fixed an issue where the Insert/Update action did not work when supporting two or more data sources.
Fixed an issue where a failed import did not send a notification and did not trigger the disable job feature after the configured number of failed attempts.
Fixed an issue where viewing the summary details returned "Buffer cannot be null".
Fixed an issue where the Last Run date column was blank when viewing scheduled jobs.
Fixed an issue for iMIS Professional where the Payments data source was not valid for that version.

iDMS Release Notes 2022

iDMS 1.18 — December 2022 (12/28/2022)

Hotfixes

February 17, 2023 (v1.18.8) — Fixed an issue where matching across entities did not produce the expected results.
February 10, 2023 (v1.18.7) — Amended how the Update action found entities.
February 9, 2023 (v1.18.6) — Fixed an issue with missing match-on field detection.
December 31, 2022 (v1.18.5) — Fixed an issue with POSTing feeds redirection.

New features

Implemented the Microsoft .NET 6 framework.

iDMS 1.17 — November 2022 (11/7/2022)

New features

Trigger an iDMS job from another source. See the online documentation.
Flexibility using the BillSubscription flag when inserting subscriptions. Set the bill amount, add a subscription without billing the contact, and more. See the enhancement details.
Handling unknown errors from the REST API. When iDMS receives a vague error from a REST API call, a stepped troubleshooting process is now provided.
Full name tribute. When adding a gift, you can now add the full name tribute rather than specifying the iMIS ID.
Clear shopping cart. You can use the Delete action to clear member shopping carts.
Skip Blank Match On. This option defaults to on. At runtime, if any match-on fields have a blank value, the record is skipped.
Improved ability to add files to File Content fields in panels. Only the public file URL is now required when adding a file to a panel field.
iDMS templates are now sorted alphabetically.

Fixes

Fixed an issue where, on Insert of a contact record, if the member type was not specified and the default member type did not have Is Member specified, the record was added as a company record. A person record is now created.
Fixed an issue where the Gift Date was not set to the Transaction Date when importing fundraising records without a specified gift date.
Fixed an issue when deleting a Company Admin relationship.
Fixed an issue when creating inactive subscriptions.
Fixed an issue where updating a panel created a new record if one was missing.
Fixed an issue where iDMS attempted to process blank rows in the import.
Fixed an issue with the license check on iUpdate jobs. Jobs now stop running when a client agreement becomes null or invalid.
Fixed an issue where iDMS did not recognize the value when using Limit Rows within an IQA.
Fixed an issue where iDMS defaulted date fields to 12:00:00 AM. The time value is now read on import.
Fixed an issue when inserting a duplicate username or login. A clear message is now returned to the user.

iDMS 1.16 — September 2022

New features

Coming soon: link your Cloud IDs. If you have multiple Cloud IDs, you can link them within your cloud dashboard under My Account, then use iUpdate to run IQAs from your linked Cloud IDs.
Import event registrations. You can now import event registrations in bulk into EMS through iImport.

Fixes

Corrected an issue where Continue On Error did not work for scheduled tasks.
Added the Incurs Shipping Charges checkbox for the Products data source.
Fixed an issue where a panel record was created even when the ID did not exist in Contact.

iDMS 1.15 — August 2022

New features

Products in Cloud Professional. Commerce products and gift items can now be created and updated in iMIS 100.3.

iDMS 1.14 — July 2022

This release focused on enhancing the user experience and adding the ability to work with invoices and dues payments.

New features

Pay open invoices. You can now pay open invoices by providing the relevant invoice information in your import file.
Overpay dues payments. Dues payments that overpay what is owed can now be imported. When a member's dues billing is overpaid, a pre-pay AR item is created for the member.
Enable and disable iSchedule tasks.

Updates and enhancements

Match on this Field language improved for clarity.
iSchedule tasks can now be sorted by column headers.

Fixes

Corrected an issue where job failure email notifications did not always execute as requested.
Corrected an issue where the Continue with Update button was not disabled when Require Match On was selected but no Match On field had been defined.
Corrected an issue where re-saving a template did not honor the previously saved category.
Corrected an issue where a scheduled task would not delete when its corresponding IQA query no longer existed.
Improved job detail logging where lengthy mappings made logged entries difficult to review.

iDMS 1.13.3 — May 2022

Released May 5, 2022.

This release focused on providing additional import destinations such as products and standalone panels, enhancing validation and error messaging, and adding new safeguards.

Hotfixes

June 22, 2022 — Corrected an issue where the state/province field was incorrectly cleared for addresses in the United Kingdom.
May 19, 2022 — Corrected an issue where IQA queries required aliases to process correctly. Field aliases are no longer necessary.
May 12, 2022 — Corrected an issue where IQA query filters incorrectly displayed as undefined.

New features

Match On Only One Record. Build a failsafe into your jobs so that if more than one record with a particular ID would be affected, the job aborts.
- This protects against unintended overwrites. For example, when importing activities, a mistake could otherwise overwrite all activities for the affected records. If a job should only look at one activity per ID, enabling this option ends the job as soon as a second match is found.
Importing products. Product variations, such as multiple color and size combinations, can now be imported.
- EMS: Product definitions can now be imported.
- iMIS 2017: Products can still be imported using the CsProduct business object. Note that other tables and objects, such as Product_Price and Product_Inventory, may also need to be updated in 2017.
Support for Insert/Update to standalone panels. Previously, you could insert or update to a standalone panel, but not both at the same time. This is particularly useful for multi-instance standalone panels.
- EMS: Single and multi-instance standalone panels can now be a destination for the Insert/Update import type.

Updates and enhancements

Billing payments now support importing a check number.
Match on nearly any contact field to make the most of any dataset you have.
Validation checks on inserts to ensure the ID is mapped.
Validation checks on contact inserts to ensure either last name or company is mapped.
Speed improvements when loading business objects, making mapping quicker.
Error logging details can now be accessed on the Log Summary screen.
Log housekeeping to keep logs clean and easy to read.
Miscellaneous updates to the iDMS infrastructure.

Fixes

Clarified error messaging when matching iMIS ID on a user-defined table.
Clarified error messaging when importing billing products and matching on Major_Key.
Clarified error messaging when an iUpdate query has been deleted or its path has changed.
Corrected an issue where billing payments displayed for iMIS 2017 environments.
Corrected an issue when deleting scheduled tasks.
Corrected an issue with expression builder fields in a query.
Corrected an issue where retrying jobs failed when working with slow queries.
Corrected an issue when importing a product without a category.
Corrected an issue when importing to multi-instance panel sources.
Corrected an issue when retrieving Cloud IDs from the service fabric.
Corrected an issue where subscriptions displayed for iMIS 2017 environments. To import subscriptions in 2017, use the CsSubscriptions business object.