You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the introduction FlexID being supported as an add-on to the consumer credit report, there are instances where retrieving a credit report file will result in a response that contains one SERVICE container for the credit report data, but also up to two other SERVICE containers for the FlexID data--one for each applicant. At present, the credit report parser looks at the first SERVICE container present to grab all the relevant data, but this is a problem if that first container is actually that of a FlexID order. There is a separate field we can also reference in our xpath to ensure the container we're using is that of the consumer credit. This should be a simple change.
The text was updated successfully, but these errors were encountered:
With the introduction FlexID being supported as an add-on to the consumer credit report, there are instances where retrieving a credit report file will result in a response that contains one SERVICE container for the credit report data, but also up to two other SERVICE containers for the FlexID data--one for each applicant. At present, the credit report parser looks at the first SERVICE container present to grab all the relevant data, but this is a problem if that first container is actually that of a FlexID order. There is a separate field we can also reference in our xpath to ensure the container we're using is that of the consumer credit. This should be a simple change.
The text was updated successfully, but these errors were encountered: