Dangl.AVACloud.Client.Shared 1.60.4

• .NETStandard 2.0

  • Dangl.Data.Shared (>= 2.5.2)
  • Dangl.Identity.Client (>= 6.3.0)
  • Microsoft.Extensions.DependencyInjection (>= 9.0.5)

# Changelog

You can find the full changelog at [DanglDocu](https://docs.dangl-it.com/).

## v1.60.4:
- Changed the `DisableItemNumberIdentifierTransformations` option when importing GAEB files. For GAEB XML source files, this option now only results in non-numerical tiers in the item numbers to be left as-is, numerical tiers will always be left-padded with zeroes to match the schema. This is to ensure that item numbers are always schema compliant, while still allowing to import item numbers that have non-numerical tiers as-is. This change is backwards compatible, but may result in different item numbers being imported than before if the source files contained non-numerical tiers and this option was enabled

## v1.60.3:
- The `ItemNumberSchemaTierDto.Alignment` property was made optional. It will still default to `ItemNumberSchemaTierAlignmentDto.Undefined` as an enum value when creating new instances, and will always have a value when returned from the API

## v1.60.1:
- Fixed a regression introduced with v1.60.0. Now, the ´ShortText` property correctly has precedence over the `HtmlShortText` property again, ensuring backwards compatibility. If you want to work with the `HtmlShortText` property, please ensure that `ShortText` is set to `null` when sending data to AVACloud

## v1.60.0:
- Added `HtmlShortText` to `IDescription` elements (`Position`, `NoteText` and `SubDescription`). This is in behavior similar to `HtmlLongText`, setting this will override the `ShortText` property. This can be used to transport text additions in short texts
- Added `DisableItemNumberIdentifierTransformations` as option when importing GAEB files. Enabling this will import the item numbers directly as-is from the GAEB file, without adjustments like padding with zeroes. This allows to preserve the item numbers exactly as given in the GAEB files, even if they are not schema compliant

## v1.59.0:
- For UBL invoices, the `CreditNote` root element is now also supported for importing, exporting and validation. If invoices of type `CreditNote` are exported to the UBL format, a `CreditNote` element will now be created instead of an `Invoice` element

## v1.58.0:
- Updated the **Dangl.AVA.Converter** dependency to allow for custom catalogue types to be transferred via the older GAEB XML V3.2 standard. This change is backwards compatible and will yield the same results for defined catalogue types in the GAEB XML schemas, but it's now also possible to exchange free text catalogues like the newer DIN 276 2018 version that was not available in the older GAEB XML V3.2 standard.

## v1.57.2:
- Updated the internal dependencies to fix a bug with calculating total prices of base positions for complementing positions

## v1.57.1:
- Added the `Invoice.SellerTaxRepresentative` property to the XRechnung endpoints

## v1.57.0:
- Added a fix that now only calculates the base position sums of complemented positions for base positions that have not `priceType.WithoutTotal`
- Added new ÖNorm destination types for the invoice formats `RE2009`, `RE2015` and `RE2021`. This now allows to create ÖNorm invoices. A proper invoice endpoint will be provided in a future update, which will then also allow setting invoice specific properties
- ÖNorm invoices can now also be imported in the ÖNorm XML format

## v1.56.0:
- The XRechnung target can now export multiple types, in addition to _UBL_ **AVACloud** now also supports _CrossIndustryInvoice_ and _FacturX (ZUGFeRD)_

## v1.55.0:
- AVACloud was updated to .NET 9

## v1.54.18:
- Added an initial invoice-to-pdf endpoint, which is using a very early form of the XRechnung to PDF conversion. This is still in a preview state and will be improved in future releases

## v1.54.15:
- The admin UI can now show clients grouped by customers, so it's possible to see aggregated total conversions for all clients of a customer

## v1.54.0:
- There is now a validation feature also for XRechnung files

## v1.53.1:
- Individual `ExecutionDescription.Block` elements now also support the `StandardizedDescription` property for GAEB im- and exports

## v1.53.0:
- Added `ItemNumberSchemaTier.Alignment` property
- When importing GAEB 2000 files with invalid item numbers, those will now tried be be preserved (and possibly corrected) instead of simply being ignored
- When exporting to Excel, it's now possible to lock all cells except those for price inputs

## v1.52.2:
- When importing Excel files, positions without total price are also now recognized if new element import is enabled
- When working with **AVA** projects, it's now possible to set `ItemNumberSchema.disableLeftPaddingTiersWithFiller` to `true` to disable automatic left-padding and filling of single tiers in item numbers

## v1.52.1:
- Fixed a bug in the AVAtoAVA conversion where the specified price rounding mode was not used for total prices if the option to force strict total prices was disabled

## v1.52.0:
- **AVACloud** now supports XRechnung, the German e-invoicing format. Both a direct representation of the invoice model is available, as well as a conversion to and from the known **Dangl.AVA** format via a wrapper class with additional, required invoice data. This is currently in a preview state, please contact us if you want to learn more about this feature. The documentation is not yet finished, and the feature might change until it's declared stable. In the future, XRechnung might also be available separately as an addon, and may not be part of the core AVACloud offering.

## v1.51.0:
- When converting AVA to REB, it's now possible to specify the last used row address. This is useful for incremental exports, where the new file should continue with the next free address after the last used one in a previous quantity determination