Core 2.0.746

No breaking changes.

🆕 Matching settings to functionalities​

A new batch of settings have had functionalities attached.

You can read more about the details below, or check the affected settings directly.

✅ SDI & NTH Support​

The GetInvoiceExportDocuments service is now being utilized to support both SDI and NTH.

An announcement via our notes will be made once this is also supported via the Admin Suite chapter E-invoices.

✅ Global Blue changes​

We made some changes when it comes to eligibility for using Global Blue tax free forms.

🆕 BackendSystemID in Event Exports from Cases​

We've added the BackendSystemID to the event export target for Cases. More on event export targets here

🆕 CustomFieldBackendID in GetRepair​

To help simplify integrations with third parties, if custom fields have a BackendID, it will now be included in the GetRepair response as CustomFieldBackendID.

✅ IncludedProductProperties in ListProductGiftCards​

To make for a more efficient use of service calls, we've added a new optional property to the ListProductGiftCards service call: IncludedProductProperties.

{
  IncludedProductProperties: ["backend_id", "custom_id"],
}

{
  Result: {
  "PageConfig": {
    "Filter": {},
    "Start": 0,
    "Limit": 50,
    "SortDirection": 0
  },
  "Page": [
    {
      "ID": 1,
      "ProductID": 894,
      "ProductName": "Example Giftcard",
      "Product": {
        "product_id": 1234,
        "backend_id": "Example_Giftcard",
        "custom_id": "eg1234"
      },
      "GiftCardConfigurationID": 2,
      "GiftCardConfigurationName": "INTERSOLVE",
      "IsDigital": false
    },
    ...
  ],
  ...
 }
}

🆕 OrderLineID in Orders Data lake export​

The Orders Data lake export now contains an OrderlineID property in the OrderLines' OrderLedgers object.

🆕 BackendSystemID in scripting​

You can now use a BackendSystemID when scripting. This will for one allow for easier routing and reporting of return types.

Please bear in mind however, that this property is being phased out slowly across EVA in favor of unique BackendIDs.

✅ Validating Roles on User types​

From now on, roles can only be added to user types which are explicitly specified in that role.

EVA holds many kinds of User types. When configuring Roles, you could optionally attach such user types, after which EVA would check if the user was of the right type when trying to assign that role.

Until now, if you had not added any kind of user type in a role, it would mean that the role could be added to all user types.

That changes with this Core drop in the following way:

• EVA now requires you to add user types when creating a role.
• More importantly: EVA now validates that the role matches the user type, even when no user types are specified in that (already existing) role. This means that from now on, roles can only be added to user types which are explicitly specified in that role.

🆕 SetDiscountLayerSequences​

To allow for making bulk changes in discount layers, we're introducing a new service: SetDiscountLayerSequences.

{
  "Layers": [2, 3, 5, 8, 4, 7, 6] // LayerIDs
}

✅ ExportProductBaseExcel​

The ExportProductBaseExcel service now includes a limit (up to 1.000.000 records) on the number of products that can be exported, to take Excel's limitations into account.

Additionally, the related services have been moved to async variants.

✅ UseSpecialInStoreReturn defaults to false​

The UseSpecialInStoreReturn setting, as mentioned in last week's Changes to the in-store return flow Core drop entry, now defaults to false instead of the earlier mentioned true.

🆕 PrivacyRemovalRequests​

To increase your options when it comes to clearing customer data, we are introducing two new settings.

The goal of these settings is to make sure there never are customers which are not actively needed to finalize an order.

✅ Pagination in User requirement sets​

The User requirement sets chapter now includes pagination.

🆕 Logic for preventing stencil triggers​

You can now include logic in any stencil template to prevent the stencil from being triggered based on your custom conditions.

This logic can be created as a Helper.

{{if User.CustomFields['NO_EMAILS'] == 'true'}}
  {{:~eva_template_early_exit()}}
{{/if}}

🆕 More properties in in Repairs related templates​

We have added several properties related to taxes and product properties to several templates.

🆕 Requiring custom fields for applying discounts​

We have made several changes which will soon result in the ability to create manual discounts which require custom fields to be filled.

• Resolved an issue that prevented updating the UserIdentifierRequiredForSubscription value according to the "User identifier: Request from frontend" field in subscription services.
• In case of unified orders, transfer order lines that are created as a result of lines being shipped from external orders will no longer copy the BackendID of the original lines.

  this would prevent cancelling lines that were partially shipped as there would be two order lines with the same BackendID

• Old email verification tokens will be properly invalidated.
• You can now delete roles which have an OU set attached which itself was already deleted.
• Transfer order lines will no longer have a BackendID, allowing for the use of CancelOrder again.

  these IDs don't exist outside of EVA

• The ability to generate coupons on returns (introduced in Core drop 2.0.735) is now triggered based on the ShipmentShippedConfirmation event.

  this fixes an issue for coupons that weren't generated for exchange orders

• The ReceiveShipment service now handles edge cases where purchase orders were overshipped but received with a deficit.

  this effectively allows for better balancing over multiple shipments

• Cash handler will no longer allow for notes or coins whose value is lower than or equal to 0.

🚫 Effective​

These deprecations are now effective. As of now, these services and/or fields are no longer available in EVA and can no longer be used.

Deprecated​

High​

• High HasReturns is deprecated since 2.0.746: Replaced with a new Properties/NotProperties value HasReturnLines (131072).
  • SearchOrders.HasReturns
• High Order.CreatedBy is deprecated since 2.0.746: Use CreatedByID or CreatedByFullName.
  • CreateOrderFromShoppingCartResponse.Order.CreatedBy
• High Order.HasReturns is deprecated since 2.0.746: Use the new Properties value HasReturnLines (131072).
  • CreateOrderFromShoppingCartResponse.Order.HasReturns
• High Result.CreatedBy is deprecated since 2.0.746: Use CreatedByID or CreatedByFullName.
  • GetOrderResponse.Result.CreatedBy
  • EVAPayGetInfoResponse.Result.CreatedBy
• High Result.HasReturns is deprecated since 2.0.746: Use the new Properties value HasReturnLines (131072).
  • GetOrderResponse.Result.HasReturns
  • EVAPayGetInfoResponse.Result.HasReturns
• High Result.Order.CreatedBy is deprecated since 2.0.746: Use CreatedByID or CreatedByFullName.
  • GetStockReservationTaskResponse.Result.Order.CreatedBy
• High Result.Order.HasReturns is deprecated since 2.0.746: Use the new Properties value HasReturnLines (131072).
  • GetStockReservationTaskResponse.Result.Order.HasReturns
• High Result.Page.CreatedBy is deprecated since 2.0.746: Use CreatedByID or CreatedByFullName.
  • ListOrdersForCustomerResponse.Result.Page.CreatedBy
• High Result.Page.HasReturns is deprecated since 2.0.746: Use the new Properties value HasReturnLines (131072).
  • ListOrdersForCustomerResponse.Result.Page.HasReturns
  • SearchOrdersResponse.Result.Page.HasReturns
• High Roles is deprecated since 2.0.746: Replaced by RolesWithDefault.
  • GetSharedWorkspaceByIDResponse.Roles
• High ShoppingCart.CreatedBy is deprecated since 2.0.746: Use CreatedByID or CreatedByFullName.
  • ShoppingCartResponse.ShoppingCart.CreatedBy
• High ShoppingCart.HasReturns is deprecated since 2.0.746: Use the new Properties value HasReturnLines (131072).
  • ShoppingCartResponse.ShoppingCart.HasReturns
• High Task.Order.CreatedBy is deprecated since 2.0.746: Use CreatedByID or CreatedByFullName.
  • StartReservationCleanupResponse.Task.Order.CreatedBy
• High Task.Order.HasReturns is deprecated since 2.0.746: Use the new Properties value HasReturnLines (131072).
  • StartReservationCleanupResponse.Task.Order.HasReturns
• High WorkSet.Order.CreatedBy is deprecated since 2.0.746: Use CreatedByID or CreatedByFullName.
  • StartStockReservationResponse.WorkSet.Order.CreatedBy
• High WorkSet.Order.HasReturns is deprecated since 2.0.746: Use the new Properties value HasReturnLines (131072).
  • StartStockReservationResponse.WorkSet.Order.HasReturns
• High WorkSet.Orders.CreatedBy is deprecated since 2.0.746: Use CreatedByID or CreatedByFullName.
  • CompleteReservationDeviationTask.WorkSet.Orders.CreatedBy
  • StartReservationDeviationTaskResponse.WorkSet.Orders.CreatedBy
• High WorkSet.Orders.HasReturns is deprecated since 2.0.746: Use the new Properties value HasReturnLines (131072).
  • CompleteReservationDeviationTask.WorkSet.Orders.HasReturns
  • StartReservationDeviationTaskResponse.WorkSet.Orders.HasReturns

Release dates may vary​

The exact date for deploying a Core release to production environments may vary. See How we handle Core releases for more details.