Account Details - Data Connect, Ethos Errors when user has no balance

[jmmueller-mu]

When a user doesn't have a balance, account-details pipeline returns error messages that are picked up in the Ethos Integration error logs

Application: "Data Connect"
Description: "Error response from proxied request to Data Connect. error message:Bad Request"

I then have another error immediately after:
Application: "Application no longer exists"
Description: "Error: Errors were found while validating pipeline context parameters: ["Required pipeline parameter 'ethosApiKey' was not sent."]"

How to replicate: Test card with a user who has no balance.

It would be nice to not be seeing errors, as it isn't an "error", and is cluttering up the ethos logs.

[jmmueller-mu]

[ellucianBret]

This error indicates the ethosApiKey was not passed in. The Account Details - Data Connect example does have this specified in the extension.js - https://github.com/ellucian-developer/experience-ethos-examples/blob/main/account-details-dataconnect/extension/extension.js#L20

Was this configured in Configuration -> Card Management?

[jmmueller-mu]

Yes, I have that section in extension.js and the API key is configured in Experience Configuration > Card Management > Account Details > Configuration > Ethos API Key

The card works if a user has a balance, it displays information correctly without errors to Ethos Integration. The errors only occur when they have no transactions at all.

[ellucianBret]

Check the JSON body of the response in the browser when you get the error. I suspect there is more information there. I don't think the error you are seeing related to the ethosApiKey is the error for the case you are describing.

I am guessing there is a javascript error that is happening in the JS fitting after the API call. This javascript likely needs to be modified to deal with this use case of the user not having any transactions

[ellucianBret]

You should be able to test this in the Data Connect UI -> Test, if you feed it the correct person ID and the ethosApiKey

[jmmueller-mu]

I'll give it some further testing tomorrow and see what we find in the console and the return of the API in Data Connect UI for the same person

[jmmueller-mu]

Console Log:

log-level.js:24 default log level: DEBUG
VM74:181  Data Connect Serverless APIs should be called with a specific 'accept' string. You can do this with either an 'accept' or 'acceptVersion' queryParameter
eval @ index.js:2
h @ index.js:2
eval @ index.js:2
eval @ index.js:2
asyncGeneratorStep @ asyncToGenerator.js:3
_next @ asyncToGenerator.js:17
eval @ asyncToGenerator.js:22
eval @ asyncToGenerator.js:14
it @ index.js:2
at @ index.js:2
eval @ index.js:2
h @ index.js:2
eval @ index.js:2
eval @ index.js:2
asyncGeneratorStep @ asyncToGenerator.js:3
_next @ asyncToGenerator.js:17
eval @ asyncToGenerator.js:22
eval @ asyncToGenerator.js:14
eval @ index.js:2
fetchFn @ query.js:256
run @ retryer.js:105
createRetryer @ retryer.js:153
fetch @ query.js:311
executeFetch @ queryObserver.js:195
onSubscribe @ queryObserver.js:32
subscribe @ subscribable.js:16
eval @ useBaseQuery.js:63
eval @ use-sync-external-store-shim.development.js:49
Tj @ VM74:181
unstable_runWithPriority @ VM73:26
Za @ VM74:75
Ra @ VM74:180
eval @ VM74:180
R @ VM73:18
ua.port1.onmessage @ VM73:24
VM74:181 DataQueryProvider for key: millikin-account-details-v1 mounted
index.js:2 query resource key: 'millikin-account-details-v1' time: 4246

[ellucianBret]

network traffic?

[jmmueller-mu]

And the result of the same ID in Data Connect

{
  "status": 200,
  "statusText": "",
  "data": [
    {
      "header": {
        "httpFittingRequestAttempts": 1
      },
      "payload": [
        {
          "TBRCRCP": [],
          "TBRACCD": [],
          "TBRCSUM": [],
          "TBRCBRQ": [],
          "TBRACCD_CTRL": [
            {
              "accountBalance": "0",
              "amountDue": "0",
              "authAidBalance": "0",
              "memoBalance": "0",
              "nsfCount": "0",
              "queryBalance": "0"
            }
          ]
        }
      ],
      "__type": "ETHOS_MESSAGE"
    }
  ],
  "runId": "484ce612-aab9-4246-943f-e8c423f1f559"
}

[jmmueller-mu]

But I might need to test another user. This is one we added a fake charge to and removed it from, so it is possible that would change the results. No errors in Network Tab

[ellucianBret]

network traffic when this happens should show the same payload, right?

If so, then the error is happening client side in the parse of the transactions. Likely a case I didn't have when I created this initially.

[ellucianBret]

looking for the JSON body in the network response. Might not be any error

[jmmueller-mu]

https://integrate.elluciancloud.com/api/millikin-account-details-v1?cardId=001G000000iHmxsIAC%7CMillikin%2520University%7Caccount-details-dataconnect%7CAccountDetailsDataConnectCard&cardPrefix=

[{"TBRCRCP":[],"TBRACCD":[],"TBRCSUM":[],"TBRCBRQ":[],"TBRACCD_CTRL":[{"accountBalance":"0","amountDue":"0","authAidBalance":"0","memoBalance":"0","nsfCount":"0","queryBalance":"0"}]}]

[ellucianBret]

Looks good so far. The extension UI code might not be coping with this response??

[jmmueller-mu]

That's my guess