Core 2.0.760

No breaking changes.

🆕 "To Be Delivered" Label on Invoices​

The "To Be Delivered" label has been added to certified stencils PDF invoices for endless aisle orders. This label, translated for each applicable country, appears below each product (orderline) that is scheduled for an endless aisle delivery.

"TaxDetails": [
    {
      "OrderLineID": "int",
      "Rate": "decimal",
      "Amount": "decimal",
      "Name": "string",
      "Type": "string"
    }

✅ Duplicate Receipts for Returns (Yes or No)​

You can now control whether a duplicate receipt of the original sales transaction is printed alongside the return receipt using a setting. For more details on how this works, see Duplicate Receipt Printing for Return Orders.

✅ LiveGuard images - Action may be required​

The LiveGuard engine on the Watchtower will now directly fetch the product images from the CDN if configured.

As a result the CDN url must be reachable from the Watchtower. Please add it to the firewall rules if applicable.

🆕 TransferredOrder object​

We are adding a TransferredOrder object to EVA for marking transfer orders.

This object allows you to use the same properties as for regular orders and can be used to streamline your automation of transfer orders in GR/IR suspense accounts in Cookbook 1.0 and 2.0 recipes.

For an overview of which properties these are, simply press ctrl-space while in your Cookbook editor after typing TransferredOrder..

🆕 Working on pre-orders​

The following change is introduced as part of a bigger development - this feature is not ready for use

To facilitate our work on pre-order functionality, we are adding three new properties to enable product scheduling and visibility:

• AnnouncementDate: When product details become available.
• PreSaleDate: When a product is available for pre-order.
• ShipmentDate: When the product is ready for collection or delivery.

🆕 IsUsed in discount services​

The following change is introduced as part of a bigger development - this feature is not ready for use

The following services now include the new IsUsed property:

• GetLayerGroupedDiscountsByQuery
• GetDiscountByID
• SearchDiscountsByQueryResponse

This will allow the front end to save a discount even when it's already used via a (to be created) Save as new action.

✅ TimeZone in CreateCustomer​

In order to make the use of the TimeZone property more consistent throughout EVA, the service CreateCustomer now also accepts it.

🆕 PushCompany​

You can now backfill B2B customer data using the new PushCompany service, which allows for both creating and updating company records.

Additionally we are adding an optional CompanyID property to the PushUser service to allow for associating users and companies.

{
  "BackendID": "C-309521",
  "Name": "PushCompany Async Update",
  "RegistrationNumber": "12345678901234",
  "RegistrationCity": "Utrecht",
  "RegistrationCountryID": "NL",
  "RegistrationCountrySubdivisionID": "NL-UT",
  "VatNumber": "VAT1234567819",
  "FiscalID": "FISC123434256789",
  "EstablishedDate": "2023-06-06",
  "VisitorsAddress": {
    "CountryID": "NL",
    "City": "Utrecht",
    "ZipCode": "103GM",
    "Address1": "1st street",
    "HouseNumber": 5
  },
  "InvoiceAddress": {
    "CountryID": "NL",
    "City": "Utrecht",
    "ZipCode": "103GM",
    "Address1": "1st street",
    "HouseNumber": 5
  },
  "InvoiceEmailAddress": "[email protected]",
  "ContactEmailAddress": "[email protected]",
  "ContactPhoneNumber": "0635826694",
  "AccountHolerName": "Holder Account",
  "IBAN": "234234325234234234",
  "BIC": "HBUKGB4B",
  "LogoID": "507f6278-eb0e-49f2-8397-8706388d1695",
  "WasteDisposalNumber": "123123412412411",
  "TaxOfficeNumber": "123123412412412",
  "EntityType": "some-legal-form",
  "SocialCapital": 123123,
  "IndustryCode": "some-industry-code"
}

🆕 PushCompanies​

Along with the above new service, we are also introducing its big brother: PushCompanies, to allow for pushing multiple companies at once.

{
  Companies: [ //Basically the same structure as the single-push version
    {
  "BackendID": "C-309521",
  "Name": "PushCompany Async Update",
  "RegistrationNumber": "12345678901234",
  "RegistrationCity": "Utrecht",
  "RegistrationCountryID": "NL",
  "RegistrationCountrySubdivisionID": "NL-UT",
  "VatNumber": "VAT1234567819",
  "FiscalID": "FISC123434256789",
  "EstablishedDate": "2023-06-06",
  "VisitorsAddress": {
    "CountryID": "NL",
    "City": "Utrecht",
    "ZipCode": "103GM",
    "Address1": "1st street",
    "HouseNumber": 5
  },
  "InvoiceAddress": {
    "CountryID": "NL",
    "City": "Utrecht",
    "ZipCode": "103GM",
    "Address1": "1st street",
    "HouseNumber": 5
  },
  "InvoiceEmailAddress": "[email protected]",
  "ContactEmailAddress": "[email protected]",
  "ContactPhoneNumber": "0635826694",
  "AccountHolerName": "Holder Account",
  "IBAN": "234234325234234234",
  "BIC": "HBUKGB4B",
  "LogoID": "507f6278-eb0e-49f2-8397-8706388d1695",
  "WasteDisposalNumber": "123123412412411",
  "TaxOfficeNumber": "123123412412412",
  "EntityType": "some-legal-form",
  "SocialCapital": 123123,
  "IndustryCode": "some-industry-code"
    }
  ],
  DisableEventExports: true, // optional
}

{
  SuccessfullyAdjustedCompanies: [
    {
      ID: 11
    },
    {
      ID: 12
    },
    // ...
  ],
  FailedToAdjustCompanies: [
    {
      BackendID: "company-backend-id",
      ErrorIdentifier: "CompanyErrors:BackendIDAlreadyInUse"
    },
    // ...
  ]
}

🆕 GetOrder​

We are adding two new properties to GetOrder which allow EVA to ascertain whether an order is ready for shipping, and in particular when it comes to order lines of type CarryOut:

• OpenAmountForShipmentOfCarryOut
• OpenAmountForShipment

🆕 RebalanceLoyaltyPointsForUsers​

We are adding a new service to EVA for the purpose of rebalancing the loyalty points for multiple user simultaneously: RebalanceLoyaltyPointsForUsers

{
    "LoyaltyProgramID": 99,
    "SuccessfullyAdjustedUsers": [
        {
            "UserID": 507,
            "NewLoyaltyPointBalance": 300
        }
    ],
    "FailedToAdjustUsers": [
        {
            "UserID": 2507,
            "KeepPendingPoints": true,
            "AdjustmentType": 0,
            "Points": 100,
            "ErrorIdentifier": "Users:DoesNotExist"
        }
    ],
    "Metadata": {
        "ExternalIDs": {
            "LoyaltyProgram": {
                "QA-LOYALTY-6039285023": "99"
            },
            "User": {
                "5000000025": "507"
            }
        },
        "IsAsyncResultAvailable": true
    }
}

✅ UpdateOrganizationUnit​

When services touch specific organization units, EVA will now update only those OUs, instead of reloading the entire OU cache. This should speed up the services such as UpdateOrganizationUnit.

✅ ShippingMethods:UseStrictInterbranchFiltering​

The new way of restricting what shipping methods will be displayed for what kind of order, as announced in Drop 77 can now be explicitly enabled by setting ShippingMethods:UseStrictInterbranchFiltering to true.

In practice this means when enabled, an Interbranch type order for example will only have shipping methods available marked with the Delivery type Interbranch.

🆕 More properties in VertexCalculationRequest​

To accommodate tax exempt (industrial account) transactions, the VertexCalculationRequest extension point now includes a few new properties.

    if Order.HasReturnLines and Order.HasLoyaltyProgram then

      if ol.IsPartOfLoyaltyProgram then

        if Order.LoyaltyProgram.GroupTaxExemptionCode has value then

                  set output.LineItem[i].CustomerClassCode to (from TaxExemptionReasons where Code = Order.LoyaltyProgram.GroupTaxExemptionCode select Reason)

        end

      end

    end

✅ Case-insensitive AppSettings​

The names of AppSettings are now case-insensitive. Additionally we removed some unused AppSettings related to the LiveGuard sync.

• Fixed an issue where processing the events of a Financial period more often triggered multiple Data lake exports, which resulted in duplicate files in the Financial period blob overview.
• ListUserBoughtProducts now includes the CustomProductID.
• Fixed an issue where correction rounding done for a new calculation order was applied on a different line in a return order.
• Loyalty programs can now properly be detached even from cancelled lines.
• We are fixing an issue where duplicate events are published after multiple sequential customer updates in a short time.
• Fixed an issue where when a user re-subscribed to a subscription that they had been subscribed to before, we wouldn’t send a SubscriptionChangedEvent.
• BackendIDs for a deleted loyalty program can now be reused.
• Fixed an issue with partial shipping combined with non-stock products.

  note that non-stock products are different from service products

⚡ Removed from typings​

These deprecations and settings are halfway to coming into effect. With these deprecations, the following services and/or fields are no longer be exposed by our typings. Failing to enter the mentioned required fields after the specified core release, will mean the services will no longer work.

Setting​

Highest​

• Highest Vertex:UseMappingHack is deprecated and will be enforced to False from 2.0.792: This is a temporary hack that will automatically stop working after 2.0.792.

Deprecated​

High​

• High Result.Page.Subject is deprecated and will be removed in 2.0.776: The Subject is now stored in Text.
  • ListUserInteractionsResponse.Result.Page.Subject
• High Result.Page.Type is deprecated and will be removed in 2.0.776: Use InteractionType instead.
  • ListUserInteractionsResponse.Result.Page.Type
• High Results.User is deprecated and will be removed in 2.0.776: Use UserID instead.
  • ListScriptHistoryResponse.Results.User
  • ListScriptsResponse.Results.User
• High Text is deprecated and will be removed in 2.0.776: This field is not used and will be deprecated..
  • ResendUserInteractionCommunication.Text
• High Type is deprecated and will be removed in 2.0.776: Use InteractionType instead.
  • GetUserInteractionByIDResponse.Type
• Low InitialPageConfig.Filter.Type is deprecated and will be removed in 2.0.764: Use Types instead.
  • ListInvoiceExports.InitialPageConfig.Filter.Type

🚫 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 EVA.Core.Services.Invoices.GetInvoiceExportByID is deprecated since 2.0.760: Use GetInvoiceExport instead.
  • GetInvoiceExportByID

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.