Data is getting settled in next column in BIX

General
, , ,
1

Hi ,

I have added new property into extract rule while data is being fetched the date is entering to next column other than the newly added column.

My requirement is to get fit the data into the right cell.png
My requirement is to get fit the data into the right cell.png615×189 3.4 KB

The data “D1|D3,D2|D5,D19|D28” should be like this in Code column

Thanks.

2

@Yasvanth Tanuku

:warning: This is a GenAI-powered tool. All generated answers require validation against the provided references.

Here’s a step-by-step solution to fix this issue:

1. Access and Edit the Extract Rule

  1. Open Dev Studio and navigate to the Extract rule you’re working with
  2. Click on the Extract rule to open it for editing

2. Check the Output Format Configuration

  1. In the Extract rule, go to the Output format section
  2. Click the Gear icon next to the Output format to access the configuration settings
  3. Review the property mapping for your extraction

3. Fix the Column Mapping

The issue is likely occurring because the new property you added has changed how the data is being mapped to columns. To fix this:

  1. In the property mapping configuration, ensure that the property containing your code values (with format “D1|D3,D2|D5,D19|D28”) is correctly mapped to the Code column (DF)
  2. If you see that the data is being split because commas or pipe characters are being treated as delimiters, you may need to adjust the delimiter settings or use a different approach to handle the data

4. Review Filter Criteria

  1. Navigate to the Filter Criteria tab in your Extract rule
  2. Verify that any filter conditions are set correctly and aren’t causing unexpected behavior with your data

5. Save and Test

  1. After making the necessary changes, save the Extract rule
  2. Run a test extraction to verify that the data now appears correctly in the Code column

Additional Troubleshooting Tips

If the issue persists after following these steps, you might want to try these additional approaches:

  1. Check Data Format: Ensure that the source data format matches what the extract rule expects
  2. Review BIX Logging: Check the PegaBIX log file for any error messages or warnings that might provide additional insights
  3. Consider Data Transformation: If the data format is complex, you might need to use a data transform before extraction to ensure proper formatting

References:

3

Hi @Yasvanth Tanuku,

This issue might be due to the delimiter parameter passed to the extract rule. The output looks like Bix is considering “,” as the delimiter. Passing the correct delimiter should resolve this issue.

If you are using pxExtractDatawithArgs, please pass pyArgs parameter with chosen delimiter based on your data.

Note: Pega considers “,” as the default delimiter if we don’t specify a specific delimiter.

Thanks

4

@ANANDKUMARV

thanks for the reply, yeah I figured it out that’s the issue as you mentioned . The data is being separated by ,.