Detailed Changelog for Continia Expense Management 2021 R2

This article lists all new features and bug fixes for each version of Continia Expense Management 2021 R2.

Expense Management 2021 R2 Service Pack 3

Released: April 27, 2022
App version: 8.3.0.0
FOB version: 8.03.00

New or changed features

Functional areaDescriptionId
Document ApprovalWe have added the following Event Publishers

Codeunit 6086312 CEM Approval Management
  • OnBeforeApprovalMgtCode
31358
General ApplicationWe have improved the usability when creating a new Field Type. Simply give the field a description in the corporate language and the first translation is automatically added. Then click the No. of translations to add more. The Corporate Language is defined in the Expense Management Setup. 19608
General ApplicationIt is possible that some User Delegations are invalid. Either because they were wrongly setup or because they became invalid over time. For example if a delegation owner or delegated user is no longer an Expense Management user. These user delegations are now marked as Disabled and will not be exported to Continia Online. The administrator can now easily identify disabled delegations and either fix them or remove them in the Expense User Delegation page.27907
General ApplicationWe are no longer saving the default dimensions calculated at posting time, back to the original expense document. This has been causing issues in the past and it can lead to errors when posting a document in multiple transactions. 30811
General ApplicationWe have enabled the feature of signing expense attachments digitally in the French and Belgium localizations.31662
General ApplicationWe are no longer marking the Ledger Entries as "System-Created Entry". This will allow reverting ledger entries posted by Expense Management.  It also fixes an issue in the Australian localization, where the sales taxes were not posted in the "GST Purchase Entry" and tables alike.32161
General ApplicationWe have added the following Event Publishers

Table 6086309 CEM Posting Setup
  • OnBeforeModifyExistingExpense
  • OnBeforeModifyExistingMileage

Table 6086320 CEM Expense
  • OnExpenseTypeValidateBeforeExpValidation
  • OnAfterNewCalculatedAccount
32188
MileageWe've amended the sixty day check with a crude text string comparison on the addresses in cases where geographic coordinates are not available (e.g. legacy data from prior to introduction of the feature).31850

Bug fixes

Functional areaDescriptionId
Credit Card TransactionsWe've increased the length limit of the Transaction ID to 150 characters.13728
Credit Card TransactionsWe have fixed the following error when synchronizing the activation of a bank agreement: 
  • "The bank does not exist. Identification fields and value Code='',Country/Region Code='' ""
31742
Document ApprovalWe have added a link to setup out of office approval sharing to the Approval Entries page in NAV/BC.28378
ExpensesWe have fixed an issue that was causing the "External Document No." to be empty after posting matched expenses. 31102
ExpensesWe have fixed a bug on the expense card, where for cases of reverse charge VAT, the VAT and Base Amount was displayed wrongly.31410
ExpensesWe have implemented functionality to avoid and enforce the usage of Jobs/Tasks on sales tax allocation lines. Sales Tax allocation will no longer post Job ledger entries. This is especially relevant for the Canada Sales Tax.31943
ExpensesWe have fixed an issue in MS Dynamics NAV 2009 R2, when an expense with Jobs was posted. There would have been an error like the one below.  This issue doesn't affect other versions. 
  • "Bal. Account Type must be G/L Account in Gen. Journal Line Journal Template Name='GENERAL',Journal Batch Name='EXPENSE',Line No.='0'."
32562
General ApplicationWe have fixed a caption issue on the "Field Type Dependencies" page.26878
General ApplicationWe have fixed a bug where it was possible to reopen/recreate a document from NAV/BC when that document had been deleted by the user in the app/portal.27291
General ApplicationWe have fixed an issue that was showing an error if the same filters were applied on similar fields. For example, PD-DESTINATION and P-DESTINATION.27407
General ApplicationWe have disabled the drilldown functionality on the "Continia User Name" on all the pages since it was revealing a different result than the lookup on the Continia User ID. This was not only bringing confusion but sometimes it would reveal other issues.28322
General ApplicationFunctions or actions modifying Approval Entries could in some cases experience a performance issue. This has been fixed. 28367
General ApplicationWe have fixed an issue in the addin that was setting a default zoom of 1% on the attachments. 28658
General ApplicationWe have changed the caption on an action on the bank agreement page from "Request Agreement" to "Request New Agreement".30229
General ApplicationWe have fixed a number of issues related to Continia Users with Limited Document Visibility. Some are related to approvers others are general. 
1) A Continia User with limited document visibility can only view his or hers own documents. The restriction also applied to approvers with limited document visibility. Now we allow the next approver of the document to view the document, even if otherwise limited to only view own documents. The approver would get the following error message:
  • "Document X for User Y cannot be displayed because you only have access to your own documents."

If the approver is also an expense user with delegations the message would be: 
  • "Document X for User Y cannot be displayed because you are only allowed to handle documents for the following users: Z."

Where "Document" would be either Expense, Mileage, Per Diem or Expense Report/Settlement.

2) In older versions of Expense Management the message was wrong and looked like this: 
  • "Expense Expense for X cannot be displayed because you only have access to your own documents."

3) We also found that in special cases, some users with limited document visibility would have had access to posted per diems where they shouldn't have had access. This has been fixed.
4) Opening an expense document by choosing View from the reimbursement matrix and release notification entries it was in some cases possible to view the document in the wrong page and to navigate to other documents. This has been fixed.

5) The view document action button in the reimbursement details, approval entries and release notifications had three different icons. They now all have the View icon. 

6) In the Approval Entries (Forms only), the press the Show button and then choose the View option. It would not display per diems. This has been fixed. 
7) Posted Expenses, Mileage, and Expense Report would not give an error message when a user with limited document visibility opened the Posted Document Card page. The Posted Per Diem card did give a message. This has been changed to that the logic on the Posted Card is the same as on the normal Card. 

8) We were missing the Check Data Version on several document card pages.
30712
General ApplicationWe have fixed an issue where the number of documents was not correct in the Approval Portal. 30722
General ApplicationIn the EM versions 8.01 and 4.00.06 we have corrected an issue where default dimensions were not created at posting time. Unfortunately, the change further revealed another issue: the default dimension was then used for posting and re-added on the document, instead of the dimension added by the user.30737
General ApplicationWe have fixed an issue that was calculating wrong total amounts on the Per Diems, in the Status Report.30927
General ApplicationWe have fixed a bug in NAV/BC where the first subdocument line on a Settlement (Expense Report) would not inherit the global dimensions from the main document.31238
General ApplicationA filter on a Field Type of data type "Code" would have not worked unless the value was spelled with capital letters.  This has been fixed by uppercasing the filter value.31255
General ApplicationWe have fixed a bug where an empty agreement was created, when an activation request was rejected.31300
General ApplicationWe have fixed an issue that was causing the error below. It would occur when posting a Per Diem, for a user that was part of a group and there was posting setup only for the group.
  • "There is no Posting Setup within the filter. Filters: Type: Per Diem,Type Code: ACCOMMODATION."
31553
General ApplicationWe have fixed a bug where it was possible to send a welcome mail to an Expense Management user with an "empty" link to the Expense Portal.31566
General ApplicationWe have fixed an issue when the same number series was used for both posted and un-posted settlements. In this case, the posted document would have still increased the number series number when it was not expected to do so.31575
General ApplicationWe have improved the caption on the request page of the batch posting of expenses, mileages and expense reports.31650
General ApplicationWe have fixed an error in the upload company logo functionality, which would fail silently, and roll back the changes to the company logo.32567
MileageOn the Approval Entries page, on a mileage, when choosing the action Details. You would get the error message 
  • "Allocations are not supported on mileage". 

Now it will open the page Mileage Details.

28305
MileageWe have fixed an inconsistent error which was present when posting a mileage where the default dimensions were changed during posting.
The error would come up with messages similar to the ones below.

  • "The changes to the Mileage record cannot be saved because some information on the page is not up-to-date"
30470
Per DiemWe have fixed an inconsistency error which was present when posting a per diem where the default dimensions were changed during the posting. The error would come up with messages similar to the ones below.
"The changes to the Per Diem record cannot be saved because some information on the page is not up-to-date. Close the page, reopen it, and try again."
"Inconsistent read of field(s): 'Global Dimension 2 Code', on table 'Per Diem', identification values: 'Entry No.='xxxx''"
30813
Platform and TechnologyIn rare cases wrong Lookup Values Access setup could cause the synchronization with Continia Online to fail. This has been prevented.32687

Expense Management 2021 R2 Service Pack 2, hotfix 2

Released: February 2, 2022
App version: 8.2.0.2

Only released in Business Central online.

Bug fixes

Functional areaDescription
Platform and TechnologyWhen updating to Business Central 19.3, the receipt or mileage image was no longer shown on any screens, including on the Expense page, the Mileage page, the Settlement page, and the Approval page. This meant it was not possible to see the receipt or mileage image in Business Central.

Expense Management 2021 R2 Service Pack 2, hotfix 1

Released: January 19, 2022
App version: 8.2.0.1
FOB version: 8.02.01

Bug fixes

Functional areaDescription
General ApplicationIn Expense Management version 8.1.0.1 we have corrected an issue where default dimensions were not created at the time of posting. Unfortunately, the change further revealed another issue: the default dimension was then used for posting and re-added on the document instead of the dimension added by the user. We have now corrected the issue.

Expense Management 2021 R2 Service Pack 2

Released: January 6, 2022
App version: 8.2.0.0
FOB version: 8.02.00

New or changed functionality

Functional areaDescription
General ApplicationOn the reimbursement pages it was not possible to reimburse all the users at the same time when the number for the user filter would exceed 1024 characters. When pressing the Reimburse action we now process all the users in the view.
General ApplicationWe have changed the reimbursement pages so that they only show the users from the current company. In the past all the users from all the companies were shown on the pages.
General ApplicationWe have added a new event:
Codeunit 6086312 CEM Approval Management
  • OnAfterInitApproverID
The event allows to initialize the approver.
General ApplicationWe have introduced the possibility to use Tax Area and Tax Group Code on the Mileage and Per Diems.
General ApplicationWe have added functionality to inherit Job Task default dimensions, on top of the existing default dimensions. The Job Task default dimensions have the highest priority.
General ApplicationWe have added a new event
Codeunit 6086319 CEM NAV-version Mgt.
  • OnAfterCreateJnlLineDefaultDim
This allows dimensions to be changed before posting. This event should be especially useful for adding dimensions before posting transactions.
General ApplicationWe are now creating Document Capture permission sets at the same time we are creating the Expense Management ones, in the on-premise versions. Some of these permissions sets are needed, in addition to the Expense Management ones.
General ApplicationWhen documents would have been registered in advance (for a date in the future) we would have shown an error to prevent document posting. Posting documents ahead is sometimes desired, therefore we changed the functionality to only show warnings instead.
Credit Card TransactionsWe are now copying the Transaction Business Country/Region to the Expense that is matched to.
Credit Card TransactionsIt is now possible to create statement transactions from the transaction import journal.
Credit Card TransactionsWe have made visible the Reject Reason field on the "Agreement Activation Log" page so that it's more obvious when an agrement has been rejected.
Per DiemThe default per diem rates are now created without a specific country, to improve the user experience for users that don't actually use the destination country because it is always local.
ExpensesWe have improved the posting description when posting a Settlement with expenses where the Business Vendor was specified.

Bug fixes

Functional areaDescription
General ApplicationWe have fixed an issue on the Posting Setup, when copying the Expense or Mileage Account to the actual document. If no account was found on that user, it would have taken a posting account from any other user.
General ApplicationWe have fixed an issue that was leading to desynchronization issues on subdocuments belonging to a settlement. When documents were being downloaded in Business Central, if the user would have modified the documents in the exact same split of a second, the last change of the user would have never been downloaded inside Business Central. The sub-document would have failed in the Inbox with an error.
General ApplicationWe are now preventing non-reimbursable expenses to be sent to the Lessor/Bluegarden payroll interfaces.
General ApplicationWe have fixed an issue in the Lessor integration codeunits where the Expense Management description was always overwritten by the Pay Type description.
General ApplicationIn previous versions we had blocked the possibility for specifying Field Dependencies where the TASK could expect a specific value. This check has been removed and we do now allow for this again. It is now up to the user to ensure that the selected Task Code exists in all Projects. If a required Task Code does not exist in the selected project, the dependency will simply be ignored.
General ApplicationWhen synchronizing, there was functionality to recalculate mileage across all companies. This code was triggering permission errors when the user that synchronizes would have not had permissions on all the companies. We have changed the functionality so that it skips the calculations when the user doesn't have enough permissions. We do not foresee a major downside in doing so, as this calculation was mostly for presentation purposes. A mileage will always be recalculated before posting.
General ApplicationWe have fixed a translation issue that was causing confusion when sending welcome e-mails from the Continia User Setup list. The translations affected the Danish and German languages.
General ApplicationWe have fixed the following error when loading a PDF file in the add-in. Please reinstall the add-in components.
"A generic error occurred in GDI+".
General ApplicationWe have fixed an issue in the field dependencies area, where the error below would have prevented the calculations

The length of the string is 273, but it must be less than or equal to 250 characters. Value: The following users don't have access to value SALES in the field DEPARTMENT:[A very long list of users].
General ApplicationWe have prevented the following error when synchronizing. If a user didn't have the CEM-SUPER permission set but had some basic Expense Management permissions, he would have gotten a similar error when he was trying to modify a Job or a Task, for example. The error would have occurred in areas of standard Business Central, but when using a field type was configured in Expense Management over that table (for example, Job/Task)

"You do not have the following permissions o TableData CEM Field Type: Modify".
ExpensesAttendees were not copied to the Sales Tax allocation lines in the Canadian localization, when synchronizing expenses from Continia Online.
ExpensesWhen posting a Settlement with expenses having a Business Vendor, in some cases the external document number was set from the next document.
MileageWe have prevented creating a mileage rate without starting date.
Per DiemOn the Per Diem, the number of hours was rounded to the next full hour, resulting in calculation problems when sub-rates were used.
Per DiemWhen generating demo data, the allowance codes were not set on the Per Diem Group. We have fixed the issue.
Credit Card TransactionsSome actions related to the transaction processing were not available on the Expense when there was no agreement activated. This proved to be too restrictive since transactions can be imported manually, without an agreement. We changed the functionality so that it shows Transactions related actions always when there are transactions in the inbox.

Expense Management 2021 R2, hotfix 3

Released: December 17, 2021
App version: 8.1.0.3
FOB version: 8.01.03

Bug fixes

Functional areaDescription
General ApplicationIn the Spanish localizations, the Employee number was not shown on the Continia User Setup pages because of a limitation of this type of posting. Some customers have started to use the system as such, so we have decided to keep the field even though in some situations this scenario will anyway be prevented by standard Business Central checks.

Expense Management 2021 R2, hotfix 2

Released: November 24, 2021
App version: 8.1.0.2
FOB version: 8.01.02

Bug fixes

Functional areaDescription
General ApplicationWe have fixed an error when using the business vendor feature which was showing the following message.

"Purchase Invoice EXPENSE 1 already exists for this vendor."
ExpensesWhen posting a reconciliation journal, the following error would appear if the statement lines were manually inserted (without having an underlying statement transaction).

The Bank Transaction does not exists. Identification fields and value Entry No. = "0"
ExpensesFor the Spanish localization, the Document Type is only specified when documents are posted to the business Vendor. The Document Type is no longer specified for the employee vendor.
ExpensesWe have fixed an inconsistency error which was present when posting an expense where the default dimensions were changed during the posting. The error would come up with messages similar to the ones below.

"The changes to the Expense record cannot be saved because some information on the page is not up-to-date. Close the page, reopen it, and try again."

"Inconsistent read of field(s): 'Global Dimension 2 Code', on table 'Expense', identification values: 'Entry No.='xxxx''"
Per DiemOn the Per Diem validation we would sometimes show a wrong error message similar to the one below. This is due to a wrong calculation.

“There is no rate for the destination '' for the 08-06-21.”
Per DiemWe have fixed the following error message on the Per Diem, so that it shows the correct date in the placeholder.

"There is no rate for the %2."

Expense Management 2021 R2, hotfix 1

Released: November 8, 2021
App version: 8.1.0.1
FOB version: 8.01.01

Bug fixes

Functional areaDescription
General ApplicationPre-approved settlements with amounts exceeding the pre-approved amount are now sent for approval rather than having status "Open". At the moment, this is not what happens in EM 8.01 Business Central 2019 Spring (BC14).
General ApplicationThe automatic allocation did not work in Canada, in Business Central 2019 Spring (BC14) client due to a missing object.
General ApplicationPreview posting was sometimes failing with the error below when default dimensions were configured on accounts that were external to Expense Management (for example, a G/L Account). The functionality would have tried to copy those default dimensions back to the expense document. The functionality was failing to find the Expense Management document because, in preview mode, the relation between the expense document and the un-posted document '***' doesn't exist.

The Expense Header does not exist. Identification fields and values: Document Type='Settlement',No.='***'.
General Application"Tax Area Code" and "Tax Group Code" were missing on the Settlement expense subpage.
General ApplicationWhen sending a reminder email with two or more recipients, the following error would have occured:

“The email message has been deleted by another user.”
ExpensesWhen specifying a business Vendor on the Expense, if the employee Vendor would have had a currency code, the expense could not be posted. We have, instead, created a balancing line on the same currency code.
ExpensesWe have fixed an issue where the Tax Group Code was not copied from the Expense Type setup to the Expense.
ExpensesIn a settlement where Cash and non-Cash expenses would have been found, out of which some had Jobs specified, the balancing account would have been calculated incorrectly and therefore the expense would be posted as if it was Cash when the expense was not marked as such. This is found in systems where "Matching Required" is Never.
ExpensesWhen selecting a Vendor on the expense, in some specific cases, the balancing amount was incorrectly calculated to 0. The expense could not have been posted, then. We have fixed the issue.
ExpensesOn expense with "Vendor No." specified, in some specific cases, the following error would have occurred. That was because the posting currency was incorrectly calculated.

"Currency must be in Bank Account MASTERCARD".
ExpensesWe have fixed an issue that was leading with 0 amounts in the automatic allocation lines of the sales tax. This was happening only when the Expense was not yet inserted but the Tax Area and Tax Group would be specified.
ExpensesWe have fixed an issue where automatic allocations (due to Sales Tax) would not inherit Extra Fields values from the main expense to the allocation lines.
ExpensesWhen automatically allocating due to sales taxes, the Tax Area Code was not copied to the tax lines. If "TAX AREA CODE" was a mandatory field, the expense would have encountered an error in the mobile app, preventing the sending. The user were supposed to manually type the "TAX AREA CODE" values on all the allocation lines.

Expense Management 2021 R2 Service Pack 1

Released: October 1, 2021
App version: 8.1.0.0
FOB version: 8.01.00

New or changed functionality

Functional areaDescription
General ApplicationPre-approved settlements with amounts exceeding the pre-approved amount is now send for approval, rather than having status "open". See also the changelog for the Web Approval Portal.
General ApplicationWe have added multiple new Event Publishers. The updated list can be found here.
General ApplicationWe now display validation comments on settlements.
Country and RegionalThe Faroe Islands localization is now supported in Business Central online.
Country and RegionalThe Greenland localization is now supported in Business Central online.
Credit Card TransactionsWe have added support for TAB sepparated files in the Transaction Import.
Per DiemIn the Per Diem rates page we have added an action for opening the Per Diem Groups.
Per DiemWe have introduced the possibility to control the default selections on a Per Diem, based on setup. On the Expense Management Setup the field "User chooses deductions" will make all per diem details to be set when creating new documents.

Bug fixes

Functional areaDescription
General ApplicationImproved captions on the Continia User list.
General ApplicationIt was not possible to export expense attachments in the "old" web client on NAV installations.
General ApplicationWe have fixed an issue where the payment of a document didn't change the state in the Expense App for a purchase invoice.
General ApplicationWe have added the per diem destinations in the status report.
General ApplicationImproved captions in connection with Expense Approver ID.
General ApplicationWe have added the pre-approval settlements in the status report.
General ApplicationImproved captions on the per diem detail page.
General ApplicationIn the Configured Fields form in the classic client we displayed the following message in English: "Details are only displayed for Per Diem". Now the message is translated to the user's language.
General ApplicationReopening a document was not possible if there were unproceessed inbox entries. We are now allowing reopening if the document is Pending Approval or Approved.
General ApplicationUser Delegation was translated to User Responsibility in several languages. This was fixed in the Menu and in the User Delegation Page.
General ApplicationThe Expense Management version was wrongly stated as "Expense Management 2021 R1" in the About Continia Expense Management page and in the Solution Management page. We have corrected to "Expense Management 2021 R2".
General ApplicationApproval notification was not sent in the Expense App for a document that was automatically sent for approval.

Approval notification was not sent in the Expense App for a document that was automatically approved due to company policies.
General ApplicationWe have added the pre-approval amount and status to the settlement approval entries page in both NAV/BC and the Web Approval Portal.
General ApplicationOn the Settlement Card in the Classic client (NAV 2009 R2), when displaying a Per Diem line on the Settlement, and choosing Card from the Line menu button, it would display a Mileage.
General ApplicationA settlement submitted for pre-approval was not send back to the user, when approved or rejected by his/her approver.
General ApplicationImproved captions in Dutch.
General ApplicationImproved translations on the Continia Setup User page.
General ApplicationAdded pre-approval fields to the settlement list, when the feature is enabled from Expense Management Setup.
General ApplicationForce approval of pre-approval requests would not update the pre-approval status correctly, or send the settlement back to the expense user.
ExpensesIt was not possible to add allocations to an Expense in the classic client.
ExpensesWhen expenses were allocated based on the sales tax the functionality was not calculating correctly the tax amount.
ExpensesWe have added the missing "Vendor No." field on the expense-related forms. The field is necessary to enable post-to-business-vendor functionality.
ExpensesMismatch in the decimal places on the allocations would have triggered the error below, when the expense was posted. This was due to the fact that the amounts on the allocations would not fit to the total amount, leaving some decimal differences. These errors will now be signaled in the comment section and user input will be neccessary. The error is more user friendly.

"The transaction cannot be completed because it will cause inconsistencies in the G/L Entry table. Check where and how the CONSISTENT function is used in the transaction to find the reason for the error.

Contact your system administrator."
ExpensesWhen sending a reminder email to the expense users we would in some cases give a wrong message or no message to explain the choices.

Wrong message: "This expense contains values that have not been synchronized to Continia Online. This is required before this expense can be sent to the expense user. Would you like to synchronize values with Continia Online?"

The message should have said: "Do you want to send a status e-mail to all the users or only to the selected ones?"
ExpensesWe have fixed an issue where a promoted action on the expense allocations page would have said Category 4 instead of the actual caption.
ExpensesWe have fixed an issue that didn't allow the Approver to change allocation lines.
ExpensesWe have fixed an issue where the Tax Group Code was not copied from the Expense Type setup to the Expense.
ExpensesIn some cases it was possible to edit Dimensions on approved documents. We have changed this to follow the logic on the document. So if you can edit the document, then you can edit the dimensions.
MileageIn Microsoft Dynamics NAV 2013 the menusuite was still showing the "Default Vehicle per User" page which has become obsolette once we introduced the "Default Continia User Setup" functionality. The corresponding table is deleted in the upgrade routines, so the following error was received when trying to open the page.

"Cannot build the page 6086403. The metadata object Page 6086403 was not found."
MileageIt was not possible for a user with permission to edit approved documents to edit a mileage on the card form.
Per DiemOn the Per Diem list and card we are controlling the visibility of the "Departure Country/Region" and "Destination Country/Region" based on the setup that enables multiple destinations.
Per DiemPer Diem rates are re-calculated when changing destinations.
Per DiemWhen posting a per diem with multiple destinations (which had different posting setup) the functionality would not take into consideration the different setup for each destination.
Per DiemWhen using multiple destinations on a Per Diem there was a calculation error when the user would return in the home country, after he's been travelling abroad. The rate was calculated for the foregin country instead of the home country.
Per DiemWhen enabling multiple destination on the Per Diem, the functionality was always requesting for a default Per Diem rate (countr code empty). We have avoided these error messages.
Platform and TechnologyA user with a limited permission set including CEM-NAVUSER could not use the function Send to Expense User on the pages Expense Card or Expenses.

The user would get the following message: You do not have the following permissions on TableData CEM Synchronization Log: Read.
Platform and TechnologyMany tooltips were missing in the main areas of Expense Management. We have corrected the issue.
Document ApprovalThe field Settlement Pre-approval in the Expense Management Setup page was not translated and was thus displayed in English in all local versions.
Credit Card TransactionsAttempting to send a request for activation of a bank agreement in Demo, now results in an error immediately after pressing the action.
Credit Card TransactionsAdditional filter added when linking an activated bank agreement, to avoid conflicts in cases where different banks use the same agreement no.
Credit Card TransactionsWe have disabled the "next" button in the Agreement Activation Wizard, when all required information has not been provided.
Credit Card TransactionsAdded a missing duplicate on the bank transaction id, when importing transactions with the manual import tool.
Credit Card TransactionsIn BC18 and onwards it was not possible to do field mapping. We have fixed this.

Expense Management 2021 R2

Released: September 1, 2021
App version: 8.0.0.0
FOB version: 8.00.00

New or changed functionality

Functional areaDescription
General ApplicationIt's now possible to allow selected users to edit approved documents in Expense Management. In the Continia User Setup, set the flag Can Edit Approved Documents. These users can now edit a selection of fields on documents with the status Pending Approval and Released. Fields that influence amounts on documents can't be modified unless a document is reopened and approved again.
General ApplicationIt's now possible to pre-approve settlements. The feature has to be enabled in the Expense Management Setup.
General ApplicationIt's now possible to post to a business vendor on an expense. This can be useful when the business vendor is known, and the transaction has to be visible in ledger entries. The functionality is activated by adding a "Vendor No." on an expense.
General ApplicationThe "send welcome email" feature has been expanded. Now, you can choose between sending/re-sending an email to a selection of users or just sending it to all the users who haven't received it yet.
General ApplicationWith the release of Expense Management 2021 R2 (8.00), we now support the modernized email communications in Dynamics 365 Business Central 2021 Wave 1 and newer. Expense Management uses the default profile when sending out emails.
General ApplicationWith the release of Expense Management 2021 R2 (8.00), Dynamics NAV 2009 RTC (Role Tailored Client) is no longer supported. NAV 2009 Classic Client will still be supported, and RTC is also still supported for Dynamics NAV 2013 and newer versions.

Even though Dynamics NAV 2009 RTC in Expense Management 2021 R2 (8.00) is no longer supported, Dynamics NAV 2009 RTC will be supported in future service packs released for Expense Management 2021 R1 (7.00)

When Expense Management 2022 R1 (9.00) is released in April 2022, no objects for the obsolete Dynamics NAV and Business Central versions will be released. Expense Management 2022 R1 (9.00) will only be released for Business Central 14 and newer versions.
General ApplicationIt's now possible to upgrade from older versions – as early as EM 2.60 – to EM 8.00 in one step. See the upgrade documentation for details.
General ApplicationThe name of the page Default Continia User Setup has been changed to Continia Users Default Setup.
General ApplicationA cue displaying the number of approval entries awaiting action has been added. When you select this tile, the Approval Entries page opens.
General ApplicationWe have marked the method CalcLookupValForFieldAndParent as "external" in the table 6086345 "CEM Field Type".
General ApplicationWhen generating demo data, an agreement with ID 11111111 was created. That no longer happens, as the new agreement activation doesn't expect an ID to be provided.
General ApplicationThe functionality that was dependent on permission set names has been improved, so that renaming permission sets will not affect behavior. In connection with this change, the functionality related to the CEM-NAVUSER permission set (limiting the documents that a user can view) was replaced by the "Limit Document Visibility" property in the Continia User Setup. The upgrade routine will update the new value.
ExpensesWe have added the possibility to specify if an attachment is recommended, optional or mandatory on an expense type. The rule will then be respected in the Expense App and the Expense Portal.
ExpensesNew fields containing the VAT amount and the amount without VAT have been added on the expense card and the expense split and allocate page.
TransactionsThe activation flow for the bank agreement has been changed. The user will be asked to provide transaction details, and if all conditions are met, Continia's support will activate the agreement.
Country and regionalSupport for per diem trips through different countries has been added.
Document approvalPerformance optimizations have been done in regard to approval flows.

Bug fixes

Functional areaDescription
General ApplicationWhen trying to export the approval template or the reminder template from the Expense Management Setup page, no message was displayed if there was no template. This has been changed, so that if there's no template, the actions Export Template and Delete Template are hidden.
General ApplicationIn Field Type Dependencies, the condition "Has a specific value" and the expectation "Must have a specific value" can only be used for field types that meet specific conditions. If used with other field types, the Field Type Dependencies page displays an error message explaining the reason why. Field types must be of the type Code, must have lookup values, and must not depend on a parent field type.
General ApplicationIn extension-based versions of Business Central, the add-in on the settlement card wasn't refreshed when navigating to per diem lines, which it is now.
General ApplicationIt was possible to post documents with a job but without a task. This was misleading, and an error message is now displayed when a task is expected.
General ApplicationThe fields Employee Number and Employee Name have been removed from the Spanish version because employee posting would still require vendor information.
General ApplicationThe Notification Outbox cue had a rather long Danish translation "Ubehandlede notifikationer". This has been changed to "Fejl".
General ApplicationThe error SET-NOT-FOUND isn't displayed anymore when a settlement is reopened.
General ApplicationIn MS Dynamics NAV 2009 RTC, the expense fact box was not displayed. This issue has been fixed.
General ApplicationA confirmation dialog that was displayed when web services were created in Expense Management has been removed. This was causing a problem when upgrading from EM 6.50 to 7.00.

"The function UpdatePerCompany in the company initialization codeunit 6086102 in company XXX. has failed due to the following error: 'Microsoft Dynamics NAV Server attempted to issue a client callback to show a confirmation dialog box: Do you want to update all web services for Continia Online? (CodeUnit 6086360 CEM Create Web Services). Client callbacks are not supported on Microsoft Dynamics NAV Server."
General ApplicationAn issue causing the error "You do no have the following permissions on CodeUnit CEM Business Setup Management Execute" when opening Business Setup was fixed.
General ApplicationA scenario where a document could be recreated by the expense user (in the Expense App or the Expense Portal) after the document was deleted from Business Central because updates were allowed has been blocked.
General ApplicationImprovements to translation quality, especially the French translation.
ExpensesBank transactions could be blocked in the Bank Transactions Inbox if the posting date was outside the allowed posting dates. For example, when the previous period had been closed, and the bank transactions arrived a few days later. It's now possible to change posting date, but only if the imported posting date is in a closed period. The error text on the Bank Transaction Inbox entry has been improved.
ExpensesWhen an expense was reopened and re-sent to the user, there would be a notification as if the document was new. The notification has been changed to reflect that it's an update.
ExpensesWhen trying to merge an allocated expense, you would get the error message "Expense %1 cannot be merged when it has been allocated to one or more lines". With this update, the parameter %1 will be updated with the expense entry number.
MileageIt was possible to change dimensions on a posted mileage. With this release, that's no longer possible.
MileageAn issue that was causing job ledger entries to be posted twice on a mileage has been fixed. The issue was introduced in EM 7.00.
Per DiemWhen a per diem with the status Pending Expense User was changed, an update was not sent to Continia Online. This issue has been fixed.