@dangl/avacloud-client-node 1.15.0 → 1.16.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1 +1 @@
1
- 2.4.24
1
+ 2.4.26
package/LICENSE.md CHANGED
@@ -1,6 +1,6 @@
1
1
  ### Licence
2
2
 
3
- #### Copyright (c) 2021 Dangl IT GmbH, [https://www.dangl-it.com](https://www.dangl-it.com)
3
+ #### Copyright (c) 2022 Dangl IT GmbH, [https://www.dangl-it.com](https://www.dangl-it.com)
4
4
 
5
5
  This software shall only be used for non-commercial evaluation purposes.
6
6
  Please contact Dangl**IT** for a commercial licence.
package/api.d.ts CHANGED
@@ -1,8 +1,8 @@
1
1
  /**
2
- * AVACloud API 1.23.3
2
+ * AVACloud API 1.26.0
3
3
  * AVACloud API specification
4
4
  *
5
- * OpenAPI spec version: 1.23.3
5
+ * OpenAPI spec version: 1.26.0
6
6
  *
7
7
  *
8
8
  * NOTE: This class is auto generated by the swagger code generator program.
@@ -13,6 +13,22 @@
13
13
  import localVarRequest = require('request');
14
14
  import http = require('http');
15
15
  /**
16
+ * This enumeration represents the status of an addendum, 'Nachtrag' in German
17
+ */
18
+ export declare class AddendumStatusDto {
19
+ static discriminator: string | undefined;
20
+ static attributeTypeMap: Array<{
21
+ name: string;
22
+ baseName: string;
23
+ type: string;
24
+ }>;
25
+ static getAttributeTypeMap(): {
26
+ name: string;
27
+ baseName: string;
28
+ type: string;
29
+ }[];
30
+ }
31
+ /**
16
32
  * Indicates the origin of an element.
17
33
  */
18
34
  export declare class AdditionTypeDto {
@@ -458,6 +474,10 @@ export declare class IElementDto {
458
474
  * This is used to store the GAEB XML Id within this IElement. This data is not used for any calculations or evaluations but only for GAEB serialization and deserialization.
459
475
  */
460
476
  'gaebXmlId'?: string;
477
+ /**
478
+ * This optional string property is shared by all IElements, and indicates if the element is part of an addendum, a 'Nachtrag' in German.
479
+ */
480
+ 'addendumNumber'?: string;
461
481
  'elementTypeDiscriminator': string;
462
482
  static discriminator: string | undefined;
463
483
  static attributeTypeMap: Array<{
@@ -632,6 +652,14 @@ export declare class ItemNumberDto {
632
652
  * This indicates if this item number is at the lot level. Find out more about lots in the documentation.
633
653
  */
634
654
  'isLot': boolean;
655
+ /**
656
+ * This is a zero based hierarchy level. It's set automatically when used in the context of a Project, and can be used to identify the hierarchy level of the current element.
657
+ */
658
+ 'hierarchyLevel': number;
659
+ /**
660
+ * This property indicates if this ItemNumber is attached to an object of the Position type.
661
+ */
662
+ 'isAttachedToPosition': boolean;
635
663
  static discriminator: string | undefined;
636
664
  static attributeTypeMap: Array<{
637
665
  name: string;
@@ -661,13 +689,25 @@ export declare class ItemNumberSchemaDto {
661
689
  */
662
690
  'separator'?: string;
663
691
  /**
664
- * This string is used to fill (left-pad) item numbers. For example, if a tier has a length of '4' but the given item number is '12', with a Filler of '0', then the final item number will be represented as '0'. This must be a single character string, if a value is given where the Length property does not evaluate to '1', the DEFAULT_FILLER '0' is used. A space is fine to use. You should ensure that you use a value different than Separator, as that might produce unexpected results. No attempt is done by the code to recover from such ambiguous configurations
692
+ * This string is used to fill (left-pad) item numbers. For example, if a tier has a length of '4' but the given item number is '12', with a Filler of '0', then the final item number will be represented as '0'. This must be a single character string, if a value is given where the Length property does not evaluate to '1', the DEFAULT_FILLER '0' is used. A space is fine to use. You should ensure that you use a value different than Separator, as that might produce unexpected results. No attempt is done by the code to recover from such ambiguous configurations.
665
693
  */
666
694
  'filler'?: string;
667
695
  /**
668
696
  * This is just a string property that can optionally be used to store additional data for this ItemNumberSchema, e.g. an identification or a type. It does not have any influence over how item numbers are generated, and is not supported in most exchange formats. However, it is used to store ÖNorm service specification structure types.
669
697
  */
670
698
  'identifier'?: string;
699
+ /**
700
+ * This property indicates if ItemNumbers using this ItemNumberSchema should skip empty group levels. This is commonly only used in GAEB files, where there might be gaps in the hierarchy of elements and position identifiers should be placed at the end of the string representation.
701
+ */
702
+ 'skipNonExistingLevelsInPositionItemNumbers': boolean;
703
+ /**
704
+ * This string is used only when the property SkipNonExistingLevelsInPositionItemNumbers in this ItemNumberSchema is also set to true. It defaults to DEFAULT_SKIPPED_TIERS_FILLER, but can be set to any string with a lenght of one. Null values or values with a longer length will lead to this property reverting back to the default value. This is used to fill skipped tiers in item numbers where a position is placed in a higher hierarchy level than what would be defined in the Tiers. For example, it could produce an item number like '01.__.02', which would indicate a skipped second level. This should be using different values than Filler and Separator, since that could cause ambiguities in the code that generates the actual item numbers. No attempt is done by the code to recover from such ambiguous configurations.
705
+ */
706
+ 'skippedTiersFiller'?: string;
707
+ /**
708
+ * This is a read-only property that indicates if this schema has a valid structure. It internally just returns the result from IsCorrectlyDefined. This will return if the ItemNumberSchema is correctly defined. For it to be correctly defined, the following conditions must be true: There may only be one lot group, if there is one, it must be at the top. Following lot levels, there may be at least one group level. After the group levels, there must be one position level. After the position level, there may be one index level. If no tiers are defined at all, this will also return false.
709
+ */
710
+ 'schemaIsCorrectlyDefined': boolean;
671
711
  static discriminator: string | undefined;
672
712
  static attributeTypeMap: Array<{
673
713
  name: string;
@@ -850,6 +890,30 @@ export declare class NoteTextDto extends IElementDto {
850
890
  * This is an identifier specific for this description. Some exchange formats, like GAEB XML, use it to identify descriptions. It's different to an elements identifier in that it should only apply to the description component, meaning the text itself.
851
891
  */
852
892
  'descriptionId'?: string;
893
+ /**
894
+ * This class models special properties that only apply to some exchange scenarios where ÖNorm is used. It is special for NoteTexts.
895
+ */
896
+ 'oenormNoteTextProperties'?: OenormNoteTextPropertiesDto;
897
+ static discriminator: string | undefined;
898
+ static attributeTypeMap: Array<{
899
+ name: string;
900
+ baseName: string;
901
+ type: string;
902
+ }>;
903
+ static getAttributeTypeMap(): {
904
+ name: string;
905
+ baseName: string;
906
+ type: string;
907
+ }[];
908
+ }
909
+ /**
910
+ * This class models special properties that only apply to some exchange scenarios where ÖNorm is used. It is special for NoteTexts.
911
+ */
912
+ export declare class OenormNoteTextPropertiesDto {
913
+ /**
914
+ * This indicates where the content of this element originates, if set. It corresponds to 'herkunftskennzeichen' in ÖNorm
915
+ */
916
+ 'originCode': OenormOriginCodeDto;
853
917
  static discriminator: string | undefined;
854
918
  static attributeTypeMap: Array<{
855
919
  name: string;
@@ -894,6 +958,10 @@ export declare class OenormPositionPropertiesDto {
894
958
  * This indicates if the ÖNorm 'wesentliche position' mark is set
895
959
  */
896
960
  'isMainPosition': boolean;
961
+ /**
962
+ * This indicates if the ÖNorm position was a 'ungeteilteposition' (undivided position). This will only be taken into account when the position is also the sole element inside it's parent group
963
+ */
964
+ 'isUndividedPosition': boolean;
897
965
  static discriminator: string | undefined;
898
966
  static attributeTypeMap: Array<{
899
967
  name: string;
@@ -1221,6 +1289,14 @@ export declare class PositionDto extends IElementDto {
1221
1289
  * This is an identifier specific for this description. Some exchange formats, like GAEB XML, use it to identify descriptions. It's different to an elements identifier in that it should only apply to the description component, meaning the text itself.
1222
1290
  */
1223
1291
  'descriptionId'?: string;
1292
+ /**
1293
+ * This is a zero based hierarchy level. It's set automatically when used in the context of a Project, and can be used to identify the hierarchy level of the current element.
1294
+ */
1295
+ 'hierarchyLevel': number;
1296
+ /**
1297
+ * This indicates, if this element is part of an addendum an, if yes, with what status.
1298
+ */
1299
+ 'addendumStatus'?: AddendumStatusDto;
1224
1300
  static discriminator: string | undefined;
1225
1301
  static attributeTypeMap: Array<{
1226
1302
  name: string;
@@ -1840,6 +1916,14 @@ export declare class ServiceSpecificationDto {
1840
1916
  * This should specify how the approval is performed by the buyer. This matches \"AcceptType\" in GAEB
1841
1917
  */
1842
1918
  'typeOfApproval'?: string;
1919
+ /**
1920
+ * This optional string property is shared by all IElements, and indicates if the element is part of an addendum, a 'Nachtrag' in German.
1921
+ */
1922
+ 'addendumNumber'?: string;
1923
+ /**
1924
+ * This indicates, if this element is part of an addendum an, if yes, with what status.
1925
+ */
1926
+ 'addendumStatus'?: AddendumStatusDto;
1843
1927
  static discriminator: string | undefined;
1844
1928
  static attributeTypeMap: Array<{
1845
1929
  name: string;
@@ -1959,6 +2043,14 @@ export declare class ServiceSpecificationGroupDto extends IElementDto {
1959
2043
  * This class models special properties that only apply to some exchange scenarios where ÖNorm is used.
1960
2044
  */
1961
2045
  'oenormProperties'?: OenormPropertiesDto;
2046
+ /**
2047
+ * This is a zero based hierarchy level. It's set automatically when used in the context of a Project, and can be used to identify the hierarchy level of the current element.
2048
+ */
2049
+ 'hierarchyLevel': number;
2050
+ /**
2051
+ * This indicates, if this element is part of an addendum an, if yes, with what status.
2052
+ */
2053
+ 'addendumStatus'?: AddendumStatusDto;
1962
2054
  static discriminator: string | undefined;
1963
2055
  static attributeTypeMap: Array<{
1964
2056
  name: string;
@@ -2297,9 +2389,10 @@ export declare class AslvConversionApi {
2297
2389
  * @param targetExchangePhaseTransform Defaults to none, meaning no transformation will be done
2298
2390
  * @param enforceStrictOfferPhaseLongTextOutput Defaults to false. If this is enabled, exported long texts to GAEB XML that use text additions will be strictly schema compliant. If this is not enabled, any text that is marked to contain a text addition is exported in full to ensure that incorrectly used text additions are still preserved in the export.
2299
2391
  * @param exportQuantityDetermination Defaults to false. If this is enabled, quantities are exported in detail in GAEB XML targets via the &#39;QtyDeterm&#39; (Quantity Determination, or Quantity Take Off) fields. To control this, you can set custom quantity calculations in the &#39;QuantityComponents&#39; property of positions. Please see the entry for &#39;Quantity Determination&#39; in the Dangl.AVA HowTo documentation section. Please be advised that enabling this might export data that was not intended to be exported, like internal quantity calculation details, depending on what data you put in the &#39;QuantityComponents&#39; property.
2392
+ * @param removeUnprintableCharactersFromTexts If this is enabled, unprintable characters are removed from text elements. Otherwise, the conversion might fail in case some text content contains characters that are not allowed in XML output formats.
2300
2393
  * @param {*} [options] Override http request options.
2301
2394
  */
2302
- aslvConversionConvertToGaeb(aslvFile: FileParameter, destinationGaebType?: 'Gaeb90' | 'Gaeb2000' | 'Gaeb2000Commerce' | 'GaebXml_V3_1' | 'GaebXml_V3_2' | 'GaebXml_V3_2_Commerce' | 'GaebXml_V3_3' | 'GaebXml_V3_3_Commerce', targetExchangePhaseTransform?: 'None' | 'Base' | 'OfferRequest' | 'Offer' | 'Grant' | 'CostEstimate' | 'SideOffer', enforceStrictOfferPhaseLongTextOutput?: boolean, exportQuantityDetermination?: boolean, options?: any): Promise<{
2395
+ aslvConversionConvertToGaeb(aslvFile: FileParameter, destinationGaebType?: 'Gaeb90' | 'Gaeb2000' | 'Gaeb2000Commerce' | 'GaebXml_V3_1' | 'GaebXml_V3_2' | 'GaebXml_V3_2_Commerce' | 'GaebXml_V3_3' | 'GaebXml_V3_3_Commerce', targetExchangePhaseTransform?: 'None' | 'Base' | 'OfferRequest' | 'Offer' | 'Grant' | 'CostEstimate' | 'SideOffer', enforceStrictOfferPhaseLongTextOutput?: boolean, exportQuantityDetermination?: boolean, removeUnprintableCharactersFromTexts?: boolean, options?: any): Promise<{
2303
2396
  response: http.IncomingMessage;
2304
2397
  body: Buffer;
2305
2398
  }>;
@@ -2310,9 +2403,10 @@ export declare class AslvConversionApi {
2310
2403
  * @param destinationOenormType Defaults to Lv2015
2311
2404
  * @param tryRepairProjectStructure Defaults to false. If this is enabled, the converter will try to ensure that the project structure can be mapped to Oenorm. It might introduce additional group levels to ensure a compatible target
2312
2405
  * @param skipTryEnforceSchemaCompliantXmlOutput If this option is enabled, AVACloud will not attempt to force a schema-compliant Xml output for ÖNorm targets that are Xml based. By default, AVACloud will try to add required fields, even if no data is present, with sensible defaults. This behavior can be disabled with this option.
2406
+ * @param removeUnprintableCharactersFromTexts If this is enabled, unprintable characters are removed from text elements. Otherwise, the conversion might fail in case some text content contains characters that are not allowed in XML output formats.
2313
2407
  * @param {*} [options] Override http request options.
2314
2408
  */
2315
- aslvConversionConvertToOenorm(aslvFile: FileParameter, destinationOenormType?: 'Lv2015' | 'Lb2015' | 'B2063' | 'Lv2009' | 'Lb2009' | 'Lv2021' | 'Lb2021', tryRepairProjectStructure?: boolean, skipTryEnforceSchemaCompliantXmlOutput?: boolean, options?: any): Promise<{
2409
+ aslvConversionConvertToOenorm(aslvFile: FileParameter, destinationOenormType?: 'Lv2015' | 'Lb2015' | 'B2063' | 'Lv2009' | 'Lb2009' | 'Lv2021' | 'Lb2021', tryRepairProjectStructure?: boolean, skipTryEnforceSchemaCompliantXmlOutput?: boolean, removeUnprintableCharactersFromTexts?: boolean, options?: any): Promise<{
2316
2410
  response: http.IncomingMessage;
2317
2411
  body: Buffer;
2318
2412
  }>;
@@ -2338,11 +2432,12 @@ export declare class AvaConversionApi {
2338
2432
  *
2339
2433
  * @summary Converts Dangl.AVA projects to Dangl.AVA. This is useful when you want to generate the calculated properties.
2340
2434
  * @param avaProject The Dangl.AVA project
2435
+ * @param tryAutoGenerateItemNumbersAndSchema If this is set to true, AVACloud will try to generate item numbers and an item number schema automatically for the input project. The operation will not have any effect if either an item number schema is already present, or if any of the elements already has an item number.
2341
2436
  * @param removePlainTextLongTexts If set to true, plain text long texts will be removed from the output to reduce response sizes
2342
2437
  * @param removeHtmlLongTexts If set to true, html long texts will be removed from the output to reduce response sizes
2343
2438
  * @param {*} [options] Override http request options.
2344
2439
  */
2345
- avaConversionConvertToAva(avaProject: ProjectDto, removePlainTextLongTexts?: boolean, removeHtmlLongTexts?: boolean, options?: any): Promise<{
2440
+ avaConversionConvertToAva(avaProject: ProjectDto, tryAutoGenerateItemNumbersAndSchema?: boolean, removePlainTextLongTexts?: boolean, removeHtmlLongTexts?: boolean, options?: any): Promise<{
2346
2441
  response: http.IncomingMessage;
2347
2442
  body: ProjectDto;
2348
2443
  }>;
@@ -2350,12 +2445,13 @@ export declare class AvaConversionApi {
2350
2445
  *
2351
2446
  * @summary Converts Dangl.AVA projects to Excel
2352
2447
  * @param avaProject The Dangl.AVA project
2448
+ * @param tryAutoGenerateItemNumbersAndSchema If this is set to true, AVACloud will try to generate item numbers and an item number schema automatically for the input project. The operation will not have any effect if either an item number schema is already present, or if any of the elements already has an item number.
2353
2449
  * @param writePrices Defaults to true
2354
2450
  * @param writeLongTexts Defaults to true
2355
2451
  * @param conversionCulture The culture that should be used for the conversion process, to have localized Excel files
2356
2452
  * @param {*} [options] Override http request options.
2357
2453
  */
2358
- avaConversionConvertToExcel(avaProject: ProjectDto, writePrices?: boolean, writeLongTexts?: boolean, conversionCulture?: string, options?: any): Promise<{
2454
+ avaConversionConvertToExcel(avaProject: ProjectDto, tryAutoGenerateItemNumbersAndSchema?: boolean, writePrices?: boolean, writeLongTexts?: boolean, conversionCulture?: string, options?: any): Promise<{
2359
2455
  response: http.IncomingMessage;
2360
2456
  body: Buffer;
2361
2457
  }>;
@@ -2363,13 +2459,15 @@ export declare class AvaConversionApi {
2363
2459
  *
2364
2460
  * @summary Converts Dangl.AVA projects to GAEB
2365
2461
  * @param avaProject The Dangl.AVA project
2462
+ * @param tryAutoGenerateItemNumbersAndSchema If this is set to true, AVACloud will try to generate item numbers and an item number schema automatically for the input project. The operation will not have any effect if either an item number schema is already present, or if any of the elements already has an item number.
2366
2463
  * @param destinationGaebType Defaults to GAEB XML V3.2
2367
2464
  * @param targetExchangePhaseTransform Defaults to none, meaning no transformation will be done
2368
2465
  * @param enforceStrictOfferPhaseLongTextOutput Defaults to false. If this is enabled, exported long texts to GAEB XML that use text additions will be strictly schema compliant. If this is not enabled, any text that is marked to contain a text addition is exported in full to ensure that incorrectly used text additions are still preserved in the export.
2369
2466
  * @param exportQuantityDetermination Defaults to false. If this is enabled, quantities are exported in detail in GAEB XML targets via the &#39;QtyDeterm&#39; (Quantity Determination, or Quantity Take Off) fields. To control this, you can set custom quantity calculations in the &#39;QuantityComponents&#39; property of positions. Please see the entry for &#39;Quantity Determination&#39; in the Dangl.AVA HowTo documentation section. Please be advised that enabling this might export data that was not intended to be exported, like internal quantity calculation details, depending on what data you put in the &#39;QuantityComponents&#39; property.
2467
+ * @param removeUnprintableCharactersFromTexts If this is enabled, unprintable characters are removed from text elements. Otherwise, the conversion might fail in case some text content contains characters that are not allowed in XML output formats.
2370
2468
  * @param {*} [options] Override http request options.
2371
2469
  */
2372
- avaConversionConvertToGaeb(avaProject: ProjectDto, destinationGaebType?: 'Gaeb90' | 'Gaeb2000' | 'Gaeb2000Commerce' | 'GaebXml_V3_1' | 'GaebXml_V3_2' | 'GaebXml_V3_2_Commerce' | 'GaebXml_V3_3' | 'GaebXml_V3_3_Commerce', targetExchangePhaseTransform?: 'None' | 'Base' | 'OfferRequest' | 'Offer' | 'Grant' | 'CostEstimate' | 'SideOffer', enforceStrictOfferPhaseLongTextOutput?: boolean, exportQuantityDetermination?: boolean, options?: any): Promise<{
2470
+ avaConversionConvertToGaeb(avaProject: ProjectDto, tryAutoGenerateItemNumbersAndSchema?: boolean, destinationGaebType?: 'Gaeb90' | 'Gaeb2000' | 'Gaeb2000Commerce' | 'GaebXml_V3_1' | 'GaebXml_V3_2' | 'GaebXml_V3_2_Commerce' | 'GaebXml_V3_3' | 'GaebXml_V3_3_Commerce', targetExchangePhaseTransform?: 'None' | 'Base' | 'OfferRequest' | 'Offer' | 'Grant' | 'CostEstimate' | 'SideOffer', enforceStrictOfferPhaseLongTextOutput?: boolean, exportQuantityDetermination?: boolean, removeUnprintableCharactersFromTexts?: boolean, options?: any): Promise<{
2373
2471
  response: http.IncomingMessage;
2374
2472
  body: Buffer;
2375
2473
  }>;
@@ -2377,12 +2475,14 @@ export declare class AvaConversionApi {
2377
2475
  *
2378
2476
  * @summary Converts Dangl.AVA projects to Oenorm
2379
2477
  * @param avaProject The Dangl.AVA project
2478
+ * @param tryAutoGenerateItemNumbersAndSchema If this is set to true, AVACloud will try to generate item numbers and an item number schema automatically for the input project. The operation will not have any effect if either an item number schema is already present, or if any of the elements already has an item number.
2380
2479
  * @param destinationOenormType Defaults to Lv2015
2381
2480
  * @param tryRepairProjectStructure Defaults to false. If this is enabled, the converter will try to ensure that the project structure can be mapped to Oenorm. It might introduce additional group levels to ensure a compatible target
2382
2481
  * @param skipTryEnforceSchemaCompliantXmlOutput If this option is enabled, AVACloud will not attempt to force a schema-compliant Xml output for ÖNorm targets that are Xml based. By default, AVACloud will try to add required fields, even if no data is present, with sensible defaults. This behavior can be disabled with this option.
2482
+ * @param removeUnprintableCharactersFromTexts If this is enabled, unprintable characters are removed from text elements. Otherwise, the conversion might fail in case some text content contains characters that are not allowed in XML output formats.
2383
2483
  * @param {*} [options] Override http request options.
2384
2484
  */
2385
- avaConversionConvertToOenorm(avaProject: ProjectDto, destinationOenormType?: 'Lv2015' | 'Lb2015' | 'B2063' | 'Lv2009' | 'Lb2009' | 'Lv2021' | 'Lb2021', tryRepairProjectStructure?: boolean, skipTryEnforceSchemaCompliantXmlOutput?: boolean, options?: any): Promise<{
2485
+ avaConversionConvertToOenorm(avaProject: ProjectDto, tryAutoGenerateItemNumbersAndSchema?: boolean, destinationOenormType?: 'Lv2015' | 'Lb2015' | 'B2063' | 'Lv2009' | 'Lb2009' | 'Lv2021' | 'Lb2021', tryRepairProjectStructure?: boolean, skipTryEnforceSchemaCompliantXmlOutput?: boolean, removeUnprintableCharactersFromTexts?: boolean, options?: any): Promise<{
2386
2486
  response: http.IncomingMessage;
2387
2487
  body: Buffer;
2388
2488
  }>;
@@ -2390,9 +2490,10 @@ export declare class AvaConversionApi {
2390
2490
  *
2391
2491
  * @summary Converts Dangl.AVA projects to REB
2392
2492
  * @param avaProject The Dangl.AVA project
2493
+ * @param tryAutoGenerateItemNumbersAndSchema If this is set to true, AVACloud will try to generate item numbers and an item number schema automatically for the input project. The operation will not have any effect if either an item number schema is already present, or if any of the elements already has an item number.
2393
2494
  * @param {*} [options] Override http request options.
2394
2495
  */
2395
- avaConversionConvertToReb(avaProject: ProjectDto, options?: any): Promise<{
2496
+ avaConversionConvertToReb(avaProject: ProjectDto, tryAutoGenerateItemNumbersAndSchema?: boolean, options?: any): Promise<{
2396
2497
  response: http.IncomingMessage;
2397
2498
  body: Buffer;
2398
2499
  }>;
@@ -2400,9 +2501,10 @@ export declare class AvaConversionApi {
2400
2501
  *
2401
2502
  * @summary Converts Dangl.AVA projects to SIA 451
2402
2503
  * @param avaProject The Dangl.AVA project
2504
+ * @param tryAutoGenerateItemNumbersAndSchema If this is set to true, AVACloud will try to generate item numbers and an item number schema automatically for the input project. The operation will not have any effect if either an item number schema is already present, or if any of the elements already has an item number.
2403
2505
  * @param {*} [options] Override http request options.
2404
2506
  */
2405
- avaConversionConvertToSia(avaProject: ProjectDto, options?: any): Promise<{
2507
+ avaConversionConvertToSia(avaProject: ProjectDto, tryAutoGenerateItemNumbersAndSchema?: boolean, options?: any): Promise<{
2406
2508
  response: http.IncomingMessage;
2407
2509
  body: Buffer;
2408
2510
  }>;
@@ -2535,9 +2637,10 @@ export declare class ExcelConversionApi {
2535
2637
  * @param targetExchangePhaseTransform Defaults to none, meaning no transformation will be done
2536
2638
  * @param enforceStrictOfferPhaseLongTextOutput Defaults to false. If this is enabled, exported long texts to GAEB XML that use text additions will be strictly schema compliant. If this is not enabled, any text that is marked to contain a text addition is exported in full to ensure that incorrectly used text additions are still preserved in the export.
2537
2639
  * @param exportQuantityDetermination Defaults to false. If this is enabled, quantities are exported in detail in GAEB XML targets via the &#39;QtyDeterm&#39; (Quantity Determination, or Quantity Take Off) fields. To control this, you can set custom quantity calculations in the &#39;QuantityComponents&#39; property of positions. Please see the entry for &#39;Quantity Determination&#39; in the Dangl.AVA HowTo documentation section. Please be advised that enabling this might export data that was not intended to be exported, like internal quantity calculation details, depending on what data you put in the &#39;QuantityComponents&#39; property.
2640
+ * @param removeUnprintableCharactersFromTexts If this is enabled, unprintable characters are removed from text elements. Otherwise, the conversion might fail in case some text content contains characters that are not allowed in XML output formats.
2538
2641
  * @param {*} [options] Override http request options.
2539
2642
  */
2540
- excelConversionConvertToGaeb(excelFile: FileParameter, readNewElements?: boolean, rebuildItemNumberSchema?: boolean, destinationGaebType?: 'Gaeb90' | 'Gaeb2000' | 'Gaeb2000Commerce' | 'GaebXml_V3_1' | 'GaebXml_V3_2' | 'GaebXml_V3_2_Commerce' | 'GaebXml_V3_3' | 'GaebXml_V3_3_Commerce', targetExchangePhaseTransform?: 'None' | 'Base' | 'OfferRequest' | 'Offer' | 'Grant' | 'CostEstimate' | 'SideOffer', enforceStrictOfferPhaseLongTextOutput?: boolean, exportQuantityDetermination?: boolean, options?: any): Promise<{
2643
+ excelConversionConvertToGaeb(excelFile: FileParameter, readNewElements?: boolean, rebuildItemNumberSchema?: boolean, destinationGaebType?: 'Gaeb90' | 'Gaeb2000' | 'Gaeb2000Commerce' | 'GaebXml_V3_1' | 'GaebXml_V3_2' | 'GaebXml_V3_2_Commerce' | 'GaebXml_V3_3' | 'GaebXml_V3_3_Commerce', targetExchangePhaseTransform?: 'None' | 'Base' | 'OfferRequest' | 'Offer' | 'Grant' | 'CostEstimate' | 'SideOffer', enforceStrictOfferPhaseLongTextOutput?: boolean, exportQuantityDetermination?: boolean, removeUnprintableCharactersFromTexts?: boolean, options?: any): Promise<{
2541
2644
  response: http.IncomingMessage;
2542
2645
  body: Buffer;
2543
2646
  }>;
@@ -2550,9 +2653,10 @@ export declare class ExcelConversionApi {
2550
2653
  * @param destinationOenormType Defaults to Lv2015
2551
2654
  * @param tryRepairProjectStructure Defaults to false. If this is enabled, the converter will try to ensure that the project structure can be mapped to Oenorm. It might introduce additional group levels to ensure a compatible target
2552
2655
  * @param skipTryEnforceSchemaCompliantXmlOutput If this option is enabled, AVACloud will not attempt to force a schema-compliant Xml output for ÖNorm targets that are Xml based. By default, AVACloud will try to add required fields, even if no data is present, with sensible defaults. This behavior can be disabled with this option.
2656
+ * @param removeUnprintableCharactersFromTexts If this is enabled, unprintable characters are removed from text elements. Otherwise, the conversion might fail in case some text content contains characters that are not allowed in XML output formats.
2553
2657
  * @param {*} [options] Override http request options.
2554
2658
  */
2555
- excelConversionConvertToOenorm(excelFile: FileParameter, readNewElements?: boolean, rebuildItemNumberSchema?: boolean, destinationOenormType?: 'Lv2015' | 'Lb2015' | 'B2063' | 'Lv2009' | 'Lb2009' | 'Lv2021' | 'Lb2021', tryRepairProjectStructure?: boolean, skipTryEnforceSchemaCompliantXmlOutput?: boolean, options?: any): Promise<{
2659
+ excelConversionConvertToOenorm(excelFile: FileParameter, readNewElements?: boolean, rebuildItemNumberSchema?: boolean, destinationOenormType?: 'Lv2015' | 'Lb2015' | 'B2063' | 'Lv2009' | 'Lb2009' | 'Lv2021' | 'Lb2021', tryRepairProjectStructure?: boolean, skipTryEnforceSchemaCompliantXmlOutput?: boolean, removeUnprintableCharactersFromTexts?: boolean, options?: any): Promise<{
2556
2660
  response: http.IncomingMessage;
2557
2661
  body: Buffer;
2558
2662
  }>;
@@ -2578,11 +2682,12 @@ export declare class GaebConversionApi {
2578
2682
  *
2579
2683
  * @summary Converts GAEB files to Dangl.AVA projects
2580
2684
  * @param gaebFile The input file
2685
+ * @param supportSkippedItemNumberLevelsInPositions Defaults to &#39;false&#39;. This controls if, when deserializing GAEB files, skipped levels in position item numbers should be supported. For example, if an ItemNumberSchema defines three levels - two group levels and one position levels - but the ItemNumber of the position is just &#39;01.02&#39;, then it will be displayed as &#39;01.__.02&#39; if this is set to true.
2581
2686
  * @param removePlainTextLongTexts If set to true, plain text long texts will be removed from the output to reduce response sizes
2582
2687
  * @param removeHtmlLongTexts If set to true, html long texts will be removed from the output to reduce response sizes
2583
2688
  * @param {*} [options] Override http request options.
2584
2689
  */
2585
- gaebConversionConvertToAva(gaebFile: FileParameter, removePlainTextLongTexts?: boolean, removeHtmlLongTexts?: boolean, options?: any): Promise<{
2690
+ gaebConversionConvertToAva(gaebFile: FileParameter, supportSkippedItemNumberLevelsInPositions?: boolean, removePlainTextLongTexts?: boolean, removeHtmlLongTexts?: boolean, options?: any): Promise<{
2586
2691
  response: http.IncomingMessage;
2587
2692
  body: ProjectDto;
2588
2693
  }>;
@@ -2590,12 +2695,13 @@ export declare class GaebConversionApi {
2590
2695
  *
2591
2696
  * @summary Converts GAEB files to Excel
2592
2697
  * @param gaebFile The input file
2698
+ * @param supportSkippedItemNumberLevelsInPositions Defaults to &#39;false&#39;. This controls if, when deserializing GAEB files, skipped levels in position item numbers should be supported. For example, if an ItemNumberSchema defines three levels - two group levels and one position levels - but the ItemNumber of the position is just &#39;01.02&#39;, then it will be displayed as &#39;01.__.02&#39; if this is set to true.
2593
2699
  * @param writePrices Defaults to true
2594
2700
  * @param writeLongTexts Defaults to true
2595
2701
  * @param conversionCulture The culture that should be used for the conversion process, to have localized Excel files
2596
2702
  * @param {*} [options] Override http request options.
2597
2703
  */
2598
- gaebConversionConvertToExcel(gaebFile: FileParameter, writePrices?: boolean, writeLongTexts?: boolean, conversionCulture?: string, options?: any): Promise<{
2704
+ gaebConversionConvertToExcel(gaebFile: FileParameter, supportSkippedItemNumberLevelsInPositions?: boolean, writePrices?: boolean, writeLongTexts?: boolean, conversionCulture?: string, options?: any): Promise<{
2599
2705
  response: http.IncomingMessage;
2600
2706
  body: Buffer;
2601
2707
  }>;
@@ -2603,13 +2709,15 @@ export declare class GaebConversionApi {
2603
2709
  *
2604
2710
  * @summary Converts GAEB files to GAEB files. Used for example when transforming or repairing GAEB files.
2605
2711
  * @param gaebFile The input file
2712
+ * @param supportSkippedItemNumberLevelsInPositions Defaults to &#39;false&#39;. This controls if, when deserializing GAEB files, skipped levels in position item numbers should be supported. For example, if an ItemNumberSchema defines three levels - two group levels and one position levels - but the ItemNumber of the position is just &#39;01.02&#39;, then it will be displayed as &#39;01.__.02&#39; if this is set to true.
2606
2713
  * @param destinationGaebType Defaults to GAEB XML V3.2
2607
2714
  * @param targetExchangePhaseTransform Defaults to none, meaning no transformation will be done
2608
2715
  * @param enforceStrictOfferPhaseLongTextOutput Defaults to false. If this is enabled, exported long texts to GAEB XML that use text additions will be strictly schema compliant. If this is not enabled, any text that is marked to contain a text addition is exported in full to ensure that incorrectly used text additions are still preserved in the export.
2609
2716
  * @param exportQuantityDetermination Defaults to false. If this is enabled, quantities are exported in detail in GAEB XML targets via the &#39;QtyDeterm&#39; (Quantity Determination, or Quantity Take Off) fields. To control this, you can set custom quantity calculations in the &#39;QuantityComponents&#39; property of positions. Please see the entry for &#39;Quantity Determination&#39; in the Dangl.AVA HowTo documentation section. Please be advised that enabling this might export data that was not intended to be exported, like internal quantity calculation details, depending on what data you put in the &#39;QuantityComponents&#39; property.
2717
+ * @param removeUnprintableCharactersFromTexts If this is enabled, unprintable characters are removed from text elements. Otherwise, the conversion might fail in case some text content contains characters that are not allowed in XML output formats.
2610
2718
  * @param {*} [options] Override http request options.
2611
2719
  */
2612
- gaebConversionConvertToGaeb(gaebFile: FileParameter, destinationGaebType?: 'Gaeb90' | 'Gaeb2000' | 'Gaeb2000Commerce' | 'GaebXml_V3_1' | 'GaebXml_V3_2' | 'GaebXml_V3_2_Commerce' | 'GaebXml_V3_3' | 'GaebXml_V3_3_Commerce', targetExchangePhaseTransform?: 'None' | 'Base' | 'OfferRequest' | 'Offer' | 'Grant' | 'CostEstimate' | 'SideOffer', enforceStrictOfferPhaseLongTextOutput?: boolean, exportQuantityDetermination?: boolean, options?: any): Promise<{
2720
+ gaebConversionConvertToGaeb(gaebFile: FileParameter, supportSkippedItemNumberLevelsInPositions?: boolean, destinationGaebType?: 'Gaeb90' | 'Gaeb2000' | 'Gaeb2000Commerce' | 'GaebXml_V3_1' | 'GaebXml_V3_2' | 'GaebXml_V3_2_Commerce' | 'GaebXml_V3_3' | 'GaebXml_V3_3_Commerce', targetExchangePhaseTransform?: 'None' | 'Base' | 'OfferRequest' | 'Offer' | 'Grant' | 'CostEstimate' | 'SideOffer', enforceStrictOfferPhaseLongTextOutput?: boolean, exportQuantityDetermination?: boolean, removeUnprintableCharactersFromTexts?: boolean, options?: any): Promise<{
2613
2721
  response: http.IncomingMessage;
2614
2722
  body: Buffer;
2615
2723
  }>;
@@ -2617,12 +2725,14 @@ export declare class GaebConversionApi {
2617
2725
  *
2618
2726
  * @summary Converts GAEB files to Oenorm files
2619
2727
  * @param gaebFile The input file
2728
+ * @param supportSkippedItemNumberLevelsInPositions Defaults to &#39;false&#39;. This controls if, when deserializing GAEB files, skipped levels in position item numbers should be supported. For example, if an ItemNumberSchema defines three levels - two group levels and one position levels - but the ItemNumber of the position is just &#39;01.02&#39;, then it will be displayed as &#39;01.__.02&#39; if this is set to true.
2620
2729
  * @param destinationOenormType Defaults to Lv2015
2621
2730
  * @param tryRepairProjectStructure Defaults to false. If this is enabled, the converter will try to ensure that the project structure can be mapped to Oenorm. It might introduce additional group levels to ensure a compatible target
2622
2731
  * @param skipTryEnforceSchemaCompliantXmlOutput If this option is enabled, AVACloud will not attempt to force a schema-compliant Xml output for ÖNorm targets that are Xml based. By default, AVACloud will try to add required fields, even if no data is present, with sensible defaults. This behavior can be disabled with this option.
2732
+ * @param removeUnprintableCharactersFromTexts If this is enabled, unprintable characters are removed from text elements. Otherwise, the conversion might fail in case some text content contains characters that are not allowed in XML output formats.
2623
2733
  * @param {*} [options] Override http request options.
2624
2734
  */
2625
- gaebConversionConvertToOenorm(gaebFile: FileParameter, destinationOenormType?: 'Lv2015' | 'Lb2015' | 'B2063' | 'Lv2009' | 'Lb2009' | 'Lv2021' | 'Lb2021', tryRepairProjectStructure?: boolean, skipTryEnforceSchemaCompliantXmlOutput?: boolean, options?: any): Promise<{
2735
+ gaebConversionConvertToOenorm(gaebFile: FileParameter, supportSkippedItemNumberLevelsInPositions?: boolean, destinationOenormType?: 'Lv2015' | 'Lb2015' | 'B2063' | 'Lv2009' | 'Lb2009' | 'Lv2021' | 'Lb2021', tryRepairProjectStructure?: boolean, skipTryEnforceSchemaCompliantXmlOutput?: boolean, removeUnprintableCharactersFromTexts?: boolean, options?: any): Promise<{
2626
2736
  response: http.IncomingMessage;
2627
2737
  body: Buffer;
2628
2738
  }>;
@@ -2677,9 +2787,10 @@ export declare class OenormConversionApi {
2677
2787
  * @param targetExchangePhaseTransform Defaults to none, meaning no transformation will be done
2678
2788
  * @param enforceStrictOfferPhaseLongTextOutput Defaults to false. If this is enabled, exported long texts to GAEB XML that use text additions will be strictly schema compliant. If this is not enabled, any text that is marked to contain a text addition is exported in full to ensure that incorrectly used text additions are still preserved in the export.
2679
2789
  * @param exportQuantityDetermination Defaults to false. If this is enabled, quantities are exported in detail in GAEB XML targets via the &#39;QtyDeterm&#39; (Quantity Determination, or Quantity Take Off) fields. To control this, you can set custom quantity calculations in the &#39;QuantityComponents&#39; property of positions. Please see the entry for &#39;Quantity Determination&#39; in the Dangl.AVA HowTo documentation section. Please be advised that enabling this might export data that was not intended to be exported, like internal quantity calculation details, depending on what data you put in the &#39;QuantityComponents&#39; property.
2790
+ * @param removeUnprintableCharactersFromTexts If this is enabled, unprintable characters are removed from text elements. Otherwise, the conversion might fail in case some text content contains characters that are not allowed in XML output formats.
2680
2791
  * @param {*} [options] Override http request options.
2681
2792
  */
2682
- oenormConversionConvertToGaeb(oenormFile: FileParameter, destinationGaebType?: 'Gaeb90' | 'Gaeb2000' | 'Gaeb2000Commerce' | 'GaebXml_V3_1' | 'GaebXml_V3_2' | 'GaebXml_V3_2_Commerce' | 'GaebXml_V3_3' | 'GaebXml_V3_3_Commerce', targetExchangePhaseTransform?: 'None' | 'Base' | 'OfferRequest' | 'Offer' | 'Grant' | 'CostEstimate' | 'SideOffer', enforceStrictOfferPhaseLongTextOutput?: boolean, exportQuantityDetermination?: boolean, options?: any): Promise<{
2793
+ oenormConversionConvertToGaeb(oenormFile: FileParameter, destinationGaebType?: 'Gaeb90' | 'Gaeb2000' | 'Gaeb2000Commerce' | 'GaebXml_V3_1' | 'GaebXml_V3_2' | 'GaebXml_V3_2_Commerce' | 'GaebXml_V3_3' | 'GaebXml_V3_3_Commerce', targetExchangePhaseTransform?: 'None' | 'Base' | 'OfferRequest' | 'Offer' | 'Grant' | 'CostEstimate' | 'SideOffer', enforceStrictOfferPhaseLongTextOutput?: boolean, exportQuantityDetermination?: boolean, removeUnprintableCharactersFromTexts?: boolean, options?: any): Promise<{
2683
2794
  response: http.IncomingMessage;
2684
2795
  body: Buffer;
2685
2796
  }>;
@@ -2690,9 +2801,10 @@ export declare class OenormConversionApi {
2690
2801
  * @param destinationOenormType Defaults to Lv2015
2691
2802
  * @param tryRepairProjectStructure Defaults to false. If this is enabled, the converter will try to ensure that the project structure can be mapped to Oenorm. It might introduce additional group levels to ensure a compatible target
2692
2803
  * @param skipTryEnforceSchemaCompliantXmlOutput If this option is enabled, AVACloud will not attempt to force a schema-compliant Xml output for ÖNorm targets that are Xml based. By default, AVACloud will try to add required fields, even if no data is present, with sensible defaults. This behavior can be disabled with this option.
2804
+ * @param removeUnprintableCharactersFromTexts If this is enabled, unprintable characters are removed from text elements. Otherwise, the conversion might fail in case some text content contains characters that are not allowed in XML output formats.
2693
2805
  * @param {*} [options] Override http request options.
2694
2806
  */
2695
- oenormConversionConvertToOenorm(oenormFile: FileParameter, destinationOenormType?: 'Lv2015' | 'Lb2015' | 'B2063' | 'Lv2009' | 'Lb2009' | 'Lv2021' | 'Lb2021', tryRepairProjectStructure?: boolean, skipTryEnforceSchemaCompliantXmlOutput?: boolean, options?: any): Promise<{
2807
+ oenormConversionConvertToOenorm(oenormFile: FileParameter, destinationOenormType?: 'Lv2015' | 'Lb2015' | 'B2063' | 'Lv2009' | 'Lb2009' | 'Lv2021' | 'Lb2021', tryRepairProjectStructure?: boolean, skipTryEnforceSchemaCompliantXmlOutput?: boolean, removeUnprintableCharactersFromTexts?: boolean, options?: any): Promise<{
2696
2808
  response: http.IncomingMessage;
2697
2809
  body: Buffer;
2698
2810
  }>;
@@ -2747,9 +2859,10 @@ export declare class RebConversionApi {
2747
2859
  * @param targetExchangePhaseTransform Defaults to none, meaning no transformation will be done
2748
2860
  * @param enforceStrictOfferPhaseLongTextOutput Defaults to false. If this is enabled, exported long texts to GAEB XML that use text additions will be strictly schema compliant. If this is not enabled, any text that is marked to contain a text addition is exported in full to ensure that incorrectly used text additions are still preserved in the export.
2749
2861
  * @param exportQuantityDetermination Defaults to false. If this is enabled, quantities are exported in detail in GAEB XML targets via the &#39;QtyDeterm&#39; (Quantity Determination, or Quantity Take Off) fields. To control this, you can set custom quantity calculations in the &#39;QuantityComponents&#39; property of positions. Please see the entry for &#39;Quantity Determination&#39; in the Dangl.AVA HowTo documentation section. Please be advised that enabling this might export data that was not intended to be exported, like internal quantity calculation details, depending on what data you put in the &#39;QuantityComponents&#39; property.
2862
+ * @param removeUnprintableCharactersFromTexts If this is enabled, unprintable characters are removed from text elements. Otherwise, the conversion might fail in case some text content contains characters that are not allowed in XML output formats.
2750
2863
  * @param {*} [options] Override http request options.
2751
2864
  */
2752
- rebConversionConvertToGaeb(rebFile: FileParameter, destinationGaebType?: 'Gaeb90' | 'Gaeb2000' | 'Gaeb2000Commerce' | 'GaebXml_V3_1' | 'GaebXml_V3_2' | 'GaebXml_V3_2_Commerce' | 'GaebXml_V3_3' | 'GaebXml_V3_3_Commerce', targetExchangePhaseTransform?: 'None' | 'Base' | 'OfferRequest' | 'Offer' | 'Grant' | 'CostEstimate' | 'SideOffer', enforceStrictOfferPhaseLongTextOutput?: boolean, exportQuantityDetermination?: boolean, options?: any): Promise<{
2865
+ rebConversionConvertToGaeb(rebFile: FileParameter, destinationGaebType?: 'Gaeb90' | 'Gaeb2000' | 'Gaeb2000Commerce' | 'GaebXml_V3_1' | 'GaebXml_V3_2' | 'GaebXml_V3_2_Commerce' | 'GaebXml_V3_3' | 'GaebXml_V3_3_Commerce', targetExchangePhaseTransform?: 'None' | 'Base' | 'OfferRequest' | 'Offer' | 'Grant' | 'CostEstimate' | 'SideOffer', enforceStrictOfferPhaseLongTextOutput?: boolean, exportQuantityDetermination?: boolean, removeUnprintableCharactersFromTexts?: boolean, options?: any): Promise<{
2753
2866
  response: http.IncomingMessage;
2754
2867
  body: Buffer;
2755
2868
  }>;
@@ -2760,9 +2873,10 @@ export declare class RebConversionApi {
2760
2873
  * @param destinationOenormType Defaults to Lv2015
2761
2874
  * @param tryRepairProjectStructure Defaults to false. If this is enabled, the converter will try to ensure that the project structure can be mapped to Oenorm. It might introduce additional group levels to ensure a compatible target
2762
2875
  * @param skipTryEnforceSchemaCompliantXmlOutput If this option is enabled, AVACloud will not attempt to force a schema-compliant Xml output for ÖNorm targets that are Xml based. By default, AVACloud will try to add required fields, even if no data is present, with sensible defaults. This behavior can be disabled with this option.
2876
+ * @param removeUnprintableCharactersFromTexts If this is enabled, unprintable characters are removed from text elements. Otherwise, the conversion might fail in case some text content contains characters that are not allowed in XML output formats.
2763
2877
  * @param {*} [options] Override http request options.
2764
2878
  */
2765
- rebConversionConvertToOenorm(rebFile: FileParameter, destinationOenormType?: 'Lv2015' | 'Lb2015' | 'B2063' | 'Lv2009' | 'Lb2009' | 'Lv2021' | 'Lb2021', tryRepairProjectStructure?: boolean, skipTryEnforceSchemaCompliantXmlOutput?: boolean, options?: any): Promise<{
2879
+ rebConversionConvertToOenorm(rebFile: FileParameter, destinationOenormType?: 'Lv2015' | 'Lb2015' | 'B2063' | 'Lv2009' | 'Lb2009' | 'Lv2021' | 'Lb2021', tryRepairProjectStructure?: boolean, skipTryEnforceSchemaCompliantXmlOutput?: boolean, removeUnprintableCharactersFromTexts?: boolean, options?: any): Promise<{
2766
2880
  response: http.IncomingMessage;
2767
2881
  body: Buffer;
2768
2882
  }>;
@@ -2817,9 +2931,10 @@ export declare class SiaConversionApi {
2817
2931
  * @param targetExchangePhaseTransform Defaults to none, meaning no transformation will be done
2818
2932
  * @param enforceStrictOfferPhaseLongTextOutput Defaults to false. If this is enabled, exported long texts to GAEB XML that use text additions will be strictly schema compliant. If this is not enabled, any text that is marked to contain a text addition is exported in full to ensure that incorrectly used text additions are still preserved in the export.
2819
2933
  * @param exportQuantityDetermination Defaults to false. If this is enabled, quantities are exported in detail in GAEB XML targets via the &#39;QtyDeterm&#39; (Quantity Determination, or Quantity Take Off) fields. To control this, you can set custom quantity calculations in the &#39;QuantityComponents&#39; property of positions. Please see the entry for &#39;Quantity Determination&#39; in the Dangl.AVA HowTo documentation section. Please be advised that enabling this might export data that was not intended to be exported, like internal quantity calculation details, depending on what data you put in the &#39;QuantityComponents&#39; property.
2934
+ * @param removeUnprintableCharactersFromTexts If this is enabled, unprintable characters are removed from text elements. Otherwise, the conversion might fail in case some text content contains characters that are not allowed in XML output formats.
2820
2935
  * @param {*} [options] Override http request options.
2821
2936
  */
2822
- siaConversionConvertToGaeb(siaFile: FileParameter, destinationGaebType?: 'Gaeb90' | 'Gaeb2000' | 'Gaeb2000Commerce' | 'GaebXml_V3_1' | 'GaebXml_V3_2' | 'GaebXml_V3_2_Commerce' | 'GaebXml_V3_3' | 'GaebXml_V3_3_Commerce', targetExchangePhaseTransform?: 'None' | 'Base' | 'OfferRequest' | 'Offer' | 'Grant' | 'CostEstimate' | 'SideOffer', enforceStrictOfferPhaseLongTextOutput?: boolean, exportQuantityDetermination?: boolean, options?: any): Promise<{
2937
+ siaConversionConvertToGaeb(siaFile: FileParameter, destinationGaebType?: 'Gaeb90' | 'Gaeb2000' | 'Gaeb2000Commerce' | 'GaebXml_V3_1' | 'GaebXml_V3_2' | 'GaebXml_V3_2_Commerce' | 'GaebXml_V3_3' | 'GaebXml_V3_3_Commerce', targetExchangePhaseTransform?: 'None' | 'Base' | 'OfferRequest' | 'Offer' | 'Grant' | 'CostEstimate' | 'SideOffer', enforceStrictOfferPhaseLongTextOutput?: boolean, exportQuantityDetermination?: boolean, removeUnprintableCharactersFromTexts?: boolean, options?: any): Promise<{
2823
2938
  response: http.IncomingMessage;
2824
2939
  body: Buffer;
2825
2940
  }>;
@@ -2830,9 +2945,10 @@ export declare class SiaConversionApi {
2830
2945
  * @param destinationOenormType Defaults to Lv2015
2831
2946
  * @param tryRepairProjectStructure Defaults to false. If this is enabled, the converter will try to ensure that the project structure can be mapped to Oenorm. It might introduce additional group levels to ensure a compatible target
2832
2947
  * @param skipTryEnforceSchemaCompliantXmlOutput If this option is enabled, AVACloud will not attempt to force a schema-compliant Xml output for ÖNorm targets that are Xml based. By default, AVACloud will try to add required fields, even if no data is present, with sensible defaults. This behavior can be disabled with this option.
2948
+ * @param removeUnprintableCharactersFromTexts If this is enabled, unprintable characters are removed from text elements. Otherwise, the conversion might fail in case some text content contains characters that are not allowed in XML output formats.
2833
2949
  * @param {*} [options] Override http request options.
2834
2950
  */
2835
- siaConversionConvertToOenorm(siaFile: FileParameter, destinationOenormType?: 'Lv2015' | 'Lb2015' | 'B2063' | 'Lv2009' | 'Lb2009' | 'Lv2021' | 'Lb2021', tryRepairProjectStructure?: boolean, skipTryEnforceSchemaCompliantXmlOutput?: boolean, options?: any): Promise<{
2951
+ siaConversionConvertToOenorm(siaFile: FileParameter, destinationOenormType?: 'Lv2015' | 'Lb2015' | 'B2063' | 'Lv2009' | 'Lb2009' | 'Lv2021' | 'Lb2021', tryRepairProjectStructure?: boolean, skipTryEnforceSchemaCompliantXmlOutput?: boolean, removeUnprintableCharactersFromTexts?: boolean, options?: any): Promise<{
2836
2952
  response: http.IncomingMessage;
2837
2953
  body: Buffer;
2838
2954
  }>;