ConnectIT 365
Release notes
- idyn | Support team
- Help Desk Agent
Â
The following improvements have been implemented: |
|---|
Export: Allow value arrays directly on Data Item lines (Data Format JSON). |
Export: Added an additional key in the IDYC Export Queue Entry table for performance improvements on both export table/field monitoring and export queue processing. |
Functions: New functions ENCRYPTTEXT and DECRYPTTEXT to encrypt en decrypt strings. |
Functions: New functions GENERATEHASH and GENERATEHASHBASE64 to create hash values with support for multiple hash algorithms optionally using a key. |
Functions: New functions TRIM, TRIMSTART and TRIMEND to trim leading and or trailing characters. |
Functions: New function GETEXPORTSYSTEMIDS to retrieve System Ids from the Export Entry. Can be used in combination with processing rule to store the exported system ids when processing a (webservice) response with an import definition. |
Functions: Added addtional parameter for function FORMAT to explicitly specify which data type to validate against. |
Functions: Renamed FORMATDECIMAL to PARSEDECIMAL and changed behaviour to handle function in AL (previously handled by the ConnectIT API). |
Functions: Changed behaviour for functions REST and AZUREFUNCTION to handle function in AL (previously handled by the ConnectIT API). This results in requests to the endpoint URI being sent directly instead of through a proxy/gateway service. |
Functions: Added lookup pages for parameters that are based on enums/options to select the option value (used for functions FORMAT, GENERATEHASH and GENERATEHASHBASE64) |
Logging: (Beta feature) Added option to choose between local/internal and API logging when beta feature is enabled. |
Logging: (Beta feature) Performance improvements for local/internal logging when beta feature is enabled. |
OAuth2: Custom grant flow: Added additional check on empty token in response when using an import definition (with temporary values). |
The following issues have been resolved: |
|---|
Export: Guid data type was skipped in export. Will now be processed as Text. |
Import: XML root element before first Data Item could not always find value in structure. |
Import: Excel import could result in error on Compatilibility Id. |
Filters: (Beta feature) DateTime filter tokens could result in incorrect filterstring. e.g. >=[ISODate] resulted in >=2024-10-31 00:00..2024-10-31 23:59. This will now result in correct filter >=2024-10-31 while still supporting date (range) filters on datetime fields. |
Filters: (Beta feature) Standard text tokens ME, USER and COMPANY were also checked without using %, resulting in incorrectly using the standard tokens for regular text values. This will now expect %ME, %USER or %COMPANY. |
Tasks: Manual numbering was not allowed, even when enabled on No. Series. |
Â
The following improvements have been implemented: |
|---|
Export: New processing rule to store System IDs for exported records in Export Entry. |
Export: Re-Generate export content for failed Export Entries (requires processing rule to store System IDs). |
Import: Check external identifier on child nodes for structured data (JSON/XML) imports. |
Import: Retrieve XML element values before root data item node, which allows these values to be used in functions. |
Logging: Retrieve error information (including error message and callstack) for failed Export and Import Entries. |
Logging: Improvements in log readability by including references to tables, fields or definition lines. |
Backup: Include beta feature configuration in project and definition configuration exports. |
Events: Added additional integration events in export and import processes, including events for different methods and during generation of export content. |
The following issues have been resolved: |
|---|
Logging: Fixed invalid JsonToken issue during logging requests. While this did not result in errors in the export and import processes, this could result in incorrect error callstacks in the last known session error. |
Beta: Logging feature - Fixed issue that prevented usage for beta feature in some scenarios. |
Beta: Filter feature - Fixed issue with standard date variables/tokens (e.g. CM) that resulted in incorrect filter strings on date/time fields. |
Â
The following improvements have been implemented: |
|---|
Import: Configuration Template can now be assigned to definition line number instead of field number, which also allows assigning the template to an unmapped line. |
The following issues have been resolved: |
|---|
Import: Fixed XML XPath error on finding primary key fields/external identifier. |
Import: Fixed REST Endpoint Definition Lines - Add new line action was not visible/allowed. |
Import: Fixed FTP filename length could cause overflow on Import Entry record. |
Â
The following improvements have been implemented: |
|---|
BC24 Ready. |
Export: Allow empty content for JSON and XML. This can be used for webservice requests that require a POST or PUT without any request content. |
Export: Filter in manual export is only updated if the temporary filter was changed. |
Definition Line Management: Redesign for Move up/down actions to limit the amount of transactions to move the definition lines. |
The following issues have been resolved: |
|---|
Export: Fixed missing XML Namespaces on root Data Item node. |
Export: Fixed repeating attributes for parent Helper nodes. |
Export: Temporary filter in manual export ignored filters on empty values. |
Definition Line Management: Fixed issue with rename on records related to moved definition line (functions, output conditions) that caused the findset to not properly loop through all related records. This behaviour caused related records to not move with the moved definition line when using the Move up/down actions. |
Notifications: Fixed Windows event viewer errors when recalling notifications when the notification ID was not defined (Idyn App Management). |
Â
The following improvements have been implemented: |
|---|
Import: Additional checks during checks on external identifier to minimize reading and writing transactions on IDYC Imported Record table. |
Intercompany: Import Entries will now have their own log entry, instead of the logging details being added to the log entry for the Export Entry. |
OAuth2 Authorization: Custom grant flows now support form-urlencoded and form-data content for the token request. |
Context sensitive help pages changed to Confluence pages. |
New Beta Feature: New Key Links experience, which allows multiple instances of tables in import definitions. |
New Beta Feature: New Filter experience, which allows usage of standard filter strings. |
The following issues have been resolved: |
|---|
Export: Functions were not executed for output from BLOB, Media and MediaSet fields. |
Functions: GETCURRENTVALUE did not calculate FlowFields, resulting in an empty value. |
Â
The following improvements have been implemented: |
|---|
Export: Add Fields action also automatically cleans lines (with line renumbering) to make it easier to continue editing Definition Lines and still automatically determine parent line and indentation. |
Export/Import: Added automatic page refresh after Functions, Filters and Output Conditions pages are closed and focus is returned to the Definition Lines to display the correct count. |
OAuth2: Added scope and resource URL fields for client credentials and custom grant flows. |
Logging: The IDYC Logging Helper codeunit now contains an additional parameter (clearlogentries_days=x) that can be used in the Job Queue Entries to clear logging older then a custom (defined with x) amount of days. |
License and usage request moved/removed to decrease the amount of requests to the license server during the export/import process. |
The following issues have been resolved: |
|---|
Export: Fixed an issue where Output Conditions were not deleted when a Export Definition was deleted. |
Export: Query Parameters (used for method REST Endpoint) are now included in the definition configuration export. |
Import: Fixed an issue where filters on JSON arrays were linked to the incorrect Definition Line, causing the filters not to be checked. |
Import: Fixed an issue with indenting when importing/copying a definition from a configuration file. |
Functions: Fixed return value for CONTAINS function to properly return Yes/No as output. |
OAuth2: Fixed an issue with request with formdata contact, added an additional empty line, causing some credentials not to be recognised. |
Older release notes:
IDYN 2024