Dangl.AVACloud.Client.Public 1.52.0

• .NETStandard 2.0

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

# Changelog

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

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

## v1.50.0:
- GAEB & ÖNorm validations no longer return bad requests in case of non-readable files, but instead return validation results with a single critical error stating that the file could not be read

## v1.49.4:
- `ARM` Docker images for the self-hosted version are now also tagged for stable releases

## v1.49.1:
- The **Dangl.AVACloud.Admin** app now offers some database maintenance insights and is runnign recurring jobs for general database maintenance (SQLServer only for now)

## v1.49.0:
- Text addition identifiers in GAEB 90 exports are now left- instead of right-padded
- When exporting GAEB XML text additions that have an empty body, `<span>` element with a space character is added to the body. This is to prevent Xml schema validation to fail, since the body of a text addition can not be completely empty. When creating offer requests, it is recommended to fill the body with e.g. a placeholder text, such as `..........`
- Bugfixes in UGL exports
- The Excel dependency was updated. While functionally the same, the default implementation when deserializing Excel will no longer recalculate Excel formulas. This should not cause issues for real usage, but if Excel files are automatically generated with formulas that should be recalculated, this might cause issues.

## v1.48.0:
- Updated internal dependencies
- Fixed an issue with publishing, previously version `2.0.0` of **AVACloud** was accidentally released

## v1.47.0:
- The new property `PriceInformation.HasUnsetTaxRate` now allows differentiating between projects that have a zero `0` and those that have a `null` tax rate set
- Fixed some formula conversions in D11 and X31 files
- Exporting totals in GAEB XML now uses correct rounding, outputs may now produce slightly different values due to that

## v1.46.0:
- The backend was updated to .NET 8
- The On Premises variant is now also available as standalone Windows & Linux executables
- Fixed a bug when importing X31 files with an index in position item numbers
- Added a new controller called `FlatAvaConversionController`, which supports import and export of flat lists of elements. This is useful for scenarios where working with hierarchical structures is difficult
- The Oenorm export will now try to export correct `ftnr` values for positions, if strict Xml export options are enabled. This can possibly result in different output than before, but is necessary to export correct files

## v1.45.0:
- When importing GAEB files, it's now possible to set the `AllowLumpSumItemsWithDifferingQuantities` query parameter to allow importing of lump sum positions that have a quantity different than one. Otherwise, **AVACloud** corrects such positions to have a quantity of exactly `1`

## v1.44.0:
- Added a new query parameter `IncludeArticleNumbers` when exporting Excel files. If this is set, then a new column with article numbers, read from `position.commerceProperties.articleNumber`, will be included in the output
- When converting to `Sia`, **AVACloud** now also supports _Ifa18_ as target format. This is controlled via a new query parameter

## v1.43.0:
- Added support for `Position.PriceCatalogueData`, to transfer price estimation data in GAEB XML exchanges
- Added `Catalogue.CatalogueTypeDetail` to preserve the actual catalogue type from GAEB XML. It is now possible to differentiate between e.g. versions for the DIN 276 catalogue type

## v1.42.0:
- Added support for _IDS Connect_ import and export

## v1.14.8:
- Clients that have passed the GAEB certification with **AVACloud** as their export tool can now export their GAEB files with the mark that the application is certified. This needs to be configured by Dangl**IT** staff, please contact us to enable this for your clients

## v1.41.0:
- Added support for converting between **Dangl.AVA** and the product data formats `DATANORM` and `UGL`
- The Admin UI was updated to Angular v15
- Added support for allowing uppercase item numbers when importing GAEB files

## v1.40.0:
- `DestinationRebType.X31GaebXmlV33` was added, to allow exporting to X31 files with GAEB XML V3.3 as the target format
- Added `PostGaebSourceOptions.OutputHtmlAsXml` and `PostGaebSourceOptions.KeepEmptyHtmlText`  to be able to control how long texts in GAEB XML formats are imported
- The Admin UI was updated to Angular v15

## v1.39.0:
- The database was updated to now aggregate and archive conversion stats for older conversions. While details about single conversions are no longer kept indefinitely, client total conversions will still be available

## v1.38.0:
- Added `ServiceSpecification.BidDate`
- Added `ServiceSpecification.WarrantyBondPercentage`
- Added `ServiceSpecification.ExecutionGuaranteePercentage`
- Added `ProjectInformation.Requesters`
- Added `ProjectInformation.NotificationSites`
- Added `CommerceProperties.SubPositionIdentifier`

## v1.37.0:
- The option `RemoveUnprintableCharactersFromTexts` for XML based target formats (GAEB and ÖNorm) now defaults to `true`. If you want to serialize unprintable characters, it needs to be specifically enabled

## v1.36.0:
- Added `Position.GaebComplementingType` as a new enum property to transport information about GAEB markup / complementing types in positions. This means that in GAEB XML and GAEB 2000, the different markup types are now preserved. From a **Dangl.AVA** perspective, there are no changes required to implement on your side, but exports might now look different than before, meaning they more accurately preserve the data in the original GAEB file