Dangl.AVACloud.Client.Public 1.63.6

• .NETStandard 2.0

  • Dangl.AVACloud.Client.Shared (>= 1.63.6)

# Changelog

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

## v1.63.6:
- Added an option to disable source comments in XRechnung exports. By default, AVACloud will add a comment to the exported XRechnung XML files that indicates that the file was created with AVACloud. This can now be disabled by setting the `DisableBrandingComment` query parameter to `true` when exporting XRechnung files

## v1.63.0:
- Added a new endpoint that allows merging XRechnung invoices into PDF files as attachments. This is useful to create FacturX / ZUGFeRD invoices that contain the XRechnung XML as embedded file
- AVACloud can now also directly import PDF files with XRechnung attachments via the existing XRechnung import endpoint

## v1.62.0:
- Added a new endpoint that allows merging two AVA projects. This can be used to merge e.g. prices from a received offer into an existing project structure

## v1.61.1:
- The Docker images now use a non-root user `avaclouduser` with `uid=10001` to run AVACloud by default. This does not apply to ARM based images

## v1.61.0:
- AVACloud can now also do basic validation for GAEB 90 files
- Some bugfixes when handling XRechnung files
- The .NET clients no longer have a strong name / are no longer signed, to avoid issues when used in projects that do not use strong naming

## v1.60.12:
- Added `Position.IsMainPosition` as a new property

## v1.60.11:
- Added `DisablePriceRounding` as option for endpoints that create XRechnung files. With this option, prices will no longer be rounded to two decimal places

## v1.60.5:
- Update dependencies

## 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