Forum Discussion

ddgonzalez's avatar
ddgonzalez
Icon for OneStream Employee rankOneStream Employee
23 days ago
Solved

Connector BR fails to execute successfully

Hello Team,

I am currently writing a connector business rule that connects an EDM system to retrieve a file, apply mapping logic, and process the resulting DataTable into ACM. I have successfully implemented the same integration code for several other connectors, all of which are functioning as intended. 

However, when I attempt to apply the same logic for the Account connector, I encounter the following error:
"Index was out of range. Must be non-negative and less than the size of the collection. (Parameter 'index')"

I have rewritten the rule twice but have not been able to resolve the issue.
Do you have any insights into why this might be occurring?

Connectors
Parsing
System
  • ddgonzalez's avatar
    ddgonzalez
    16 days ago

    My team and I were able to identify the issue. The incoming values (columns) from the source system were not aligned with the available properties, which included formatting discrepancies in the supplied file and several other key details. The solution involved implementing a workaround in the code for anyone else encountering this issue.

3 Replies

  • JackLacava's avatar
    JackLacava
    Icon for OneStream Employee rankOneStream Employee
    22 days ago

    Use BRApi.ErrorLog.LogMessage to identify the line that is failing. TBH if the failing bit is in the screenshot you attached, this does not seem to be anything to do with OneStream as much as your payload not being what you expect it to be (either not something that can be parsed as correct json, or receiving an error from the external webservice about a parameter you should have passed).

  • ddgonzalez's avatar
    ddgonzalez
    Icon for OneStream Employee rankOneStream Employee
    22 days ago

    Thanks for having a look JackLacava​! 
    Per your advice and the error log, looks like the system errors out once it begins evaluating the rows within the DataTable. 
    Could this serve as evidence that there is something wrong with the incoming payload? I did notice in the supplied file that there is a formula column that has an unusual long list of characters. I suspected this to be the issue, but was not entirely certain. 

  • ddgonzalez's avatar
    ddgonzalez
    Icon for OneStream Employee rankOneStream Employee
    16 days ago

    My team and I were able to identify the issue. The incoming values (columns) from the source system were not aligned with the available properties, which included formatting discrepancies in the supplied file and several other key details. The solution involved implementing a workaround in the code for anyone else encountering this issue.