Support Article
BIX filenames are same when extracts are run from agent or UI
SA-63236
Summary
Business Intelligence Exchange (BIX) extracts are generated according to the following pattern:
BIX_classname_1.zip
The extracts now, have the current date in YYMMDD format inserted:
BIX_classname_180806_1.zip
As a result, downstream processes fail (such as data warehouse imports and reporting).
The extracts are run through an agent and a UI. The agent runs an activity that runs 36 extracts through pxExtractDataWithArgs. Whether the extracts are run from an agent or a UI, the filenames are the same.
Below are the log entries displaying the file listener retrieving files:
[FILE-Thread-265] [STANDARD] [ ] [ ] (services.file.FileActionImpl) INFO File.BIXFTPListener - Won access to //usr/local/tomcat/work/sync-data/transfer/BIX/Work/YOUR_NAME_180806_2.zip
[FILE-Thread-265] [STANDARD] [ ] [ ] (services.file.FileActionImpl) INFO File.BIXFTPListener - Won access to //usr/local/tomcat/work/sync-data/transfer/BIX/WorkYOUR_NAME_180806_2.zip
Error Messages
Not Applicable
Steps to Reproduce
Run the extracts through an agent and UI. The agent runs an activity that runs 36 extracts via pxExtractDataWithArgs.
Root Cause
This behavior is as per Pega product design.
Resolution
Here's the explanation for the reported behavior:
The BIX filename is the same due to HFix-46136.
Published February 15, 2019 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.