Question
Legato Health Technologies
Legato Health Technologies
IN
Legato Health Technologies
Posted: May 19, 2022
Last activity: May 19, 2022
Last activity: 19 May 2022 11:19 EDT
Closed
How to avoid extractidentifier, extract date time and double quotes in CSV file generated through BIX Extraction
Hi ,
Is there a way we can skip extract Identifier, extract date time and double quotes for each value in CSV Output file through BIX Extraction? Please suggest any work arounds/alternatives.
We need to provide user ability to download huge data 50K+ records having 40MB+ size from data table and generate excel/csv file. I thought BIX extraction may be on of the option but stuck with above unwanted columns and double quotes.
***Edited by Moderator Marije to add Capability tags***
***Edited by Moderator Marije to add BUG readme tags***
To see attachments, please log in.
***Edited by Moderator Marije to add BUG readme tags***
Posted: 3 years ago
Updated: 3 years ago
Updated: 19 May 2022 11:19 EDT
MOD
Pegasystems Inc.
GB
@VenkataSeshaDattK
Please see the following support article which explains the details.
Please check BIX user guide and look for ‘Unique run identifier’ topic for more information. Also see Unique run identifier
Unique run identifier only applies to CSV and database output types. As these fields are for the Unique run identifier functionality, they are not used with XML files.
Your option is to revisit the use of the extracted data to make use of the new feature. or do post processing on the excel to remove this field.
Of interest on a seperate note. Another issue resolved in Pega 8.5.6 is where now we have added DSS settings to control BIX extraction time properties.
As background:
These three columns were introduced as of Pega 7.3.1 to handle any failures during BIX incremental extraction:
pxStartCommitDateTime, pxEndCommitDateTime, and pxLastSuccessFulCommitDateTime.
Those extra 3 columns are added to handle below issues.
@VenkataSeshaDattK
Please see the following support article which explains the details.
Please check BIX user guide and look for ‘Unique run identifier’ topic for more information. Also see Unique run identifier
Unique run identifier only applies to CSV and database output types. As these fields are for the Unique run identifier functionality, they are not used with XML files.
Your option is to revisit the use of the extracted data to make use of the new feature. or do post processing on the excel to remove this field.
Of interest on a seperate note. Another issue resolved in Pega 8.5.6 is where now we have added DSS settings to control BIX extraction time properties.
As background:
These three columns were introduced as of Pega 7.3.1 to handle any failures during BIX incremental extraction:
pxStartCommitDateTime, pxEndCommitDateTime, and pxLastSuccessFulCommitDateTime.
Those extra 3 columns are added to handle below issues.
In case failure BIX incremental extraction used to starts from the last extraction date time even if some batches were processed successfully. It did not always log what was the starting and ending datetime considered for the incremental extraction. As part of this fix BIX process has been enhanced to support above use cases so that we don't extract successfully extracted data again and log start, end and last successful extract date time.
To support better backwards compatibility, this fix introduces the below DSS to allow disabling of the new columns.
BIX/disableSaveTimePropertiesInCSV
BIX/disableSaveTimePropertiesInXML
BIX/disableSaveTimePropertiesInDB
Please update to 8.5.6 in order to have access to those new settings to control your BIX extracts.
Documentation can be found here and in the Release Notes.