Hi OneStream Community,I’m relatively new to fixed-width data sources and have a couple of questions.The client has three fixed-width files that will be used as Transaction Matching data sources. Is there a way to bypass all headers, footers, blank rows, and other non-transaction rows using a single bypass rule or expression, instead of creating multiple individual bypass rules? What is the recommended way to import credit amounts as negative values? This is a one-sided match. The Amount field is displaying correctly as an absolute value of either the debit or credit amount, and the Debit field is also displaying correctly. However, the Credit field in the data set is always showing 0.Any guidance on the fixed-width field configuration or where the credit sign logic should be applied would be greatly appreciated.Thank you!

Member

Question

Fixed File Integration

Hi OneStream Community,

I’m relatively new to fixed-width data sources and have a couple of questions.

The client has three fixed-width files that will be used as Transaction Matching data sources.

Is there a way to bypass all headers, footers, blank rows, and other non-transaction rows using a single bypass rule or expression, instead of creating multiple individual bypass rules?
What is the recommended way to import credit amounts as negative values? This is a one-sided match. The Amount field is displaying correctly as an absolute value of either the debit or credit amount, and the Debit field is also displaying correctly. However, the Credit field in the data set is always showing 0.

Any guidance on the fixed-width field configuration or where the credit sign logic should be applied would be greatly appreciated.

Thank you!