jasone
Occasional Member - Level 1

Error: Cannot read properties of undefined (reading 'attendeeData')

Trying to enter doctors for a CE event and I'm getting the following error message:

 

Cannot read properties of undefined (reading 'attendeeData')

 

Any suggestions?

20 REPLIES 20
63378
Occasional Member - Level 2

We are able to retrieve a record searching both Veeva Open Data and a proprietary database, but for some records this error is returned when we try to save the searched attendee record to the expense entry.

 

jasone
Occasional Member - Level 1

Is there a solution?

KevinD
Community Manager
Community Manager

@jasone do you have a screenshot by chance? I'm not familiar with that error. Also, are you doing a Doctor lookup or manually entering the doctor's information?


Thank you,
Kevin
SAP Concur Community Manager
Did this response answer your question? Be sure to select “Accept as Solution” so your fellow community members can be helped by it as well.
jasone
Occasional Member - Level 1

I've tried to enter doctor info, first and last name and also tried just by their NPI number. The doctor comes up but when I check the box next to their name and click "add" I get the error message. I've done hundreds of expense reports and have never had this problem. Attached is a screenshot. Thanks!Screenshot 2024-09-20 094330.jpg

63378
Occasional Member - Level 2

Also have a screen shot ... from a Veeva Open Data HCP search ... if needed.  We have many problem tickets from this issue which began around last Thursday.  The ticket submitters are searching two different databases ... Veeva Open Data and a proprietary database, with somewhat differently formatted data returned.  In both situations, a record which has been returned via search cannot be posted to the expense entry .... same issue as described by Jasone, 

KevinD
Community Manager
Community Manager

@63378 looks like our Dev team is on the case. If you have Help tickets submitted, you should be kept up to date with what is happening in regards to the fix. 


Thank you,
Kevin
SAP Concur Community Manager
Did this response answer your question? Be sure to select “Accept as Solution” so your fellow community members can be helped by it as well.
athakur
Occasional Member - Level 3

Hi Kevin,

 

Is there an ETA on fix?  This is an ongoing issue since Friday.

 

Regards,

Ashish

63378
Occasional Member - Level 2

Hi Kevin.

 

We appear to be having the same issue now ... two years later ... when a user searches an HCP database the records which match the criteria are returned, an appropriate record is selected, but the record does not post in Concur ... instead the user receives the following error:  'Cannot read properties of undefined (reading attendeeData)'.  We have a large group of users who need this functionality = many help desk tickets.  Our case # is 28504011 ... it is yet to be assigned to an analyst.  We will appreciate any help you can provide to get this into the proper queue for a solution.  Thank you!

samasuraj
Occasional Member - Level 1

Hi  @63378 

 

Topic: Error: Cannot read properties of undefined (reading 'attendeeData')

 

Please check the below. Hope this helps.

-----

What SAP Concur confirmed?

In September 2024, users reported this same error across Veeva, MedPro, and Salesforce attendee connectors. An SAP Concur Community Manager confirmed that the development team was investigating the issue and advised affected customers to follow their SAP Concur support cases for updates.

 

However, I could not verify a published permanent fix or specific SAP correction note for that incident.

Original discussion: SAP Concur — attendeeData error and MedPro Connector

 

Recommended resolution — step by step

Step 1 — Test the Legacy versus New Experience

  • Open SAP Concur Expense in a desktop browser.
  • If your tenant still offers a supported option to switch attendee-search experiences, select the alternative experience.
  • Open the affected expense report.
  • Navigate to Expense Entry → Attendees → Add.
  • Search for the same MedPro healthcare professional.
  • Select the attendee and attempt to save.

A separate SAP Concur discussion from December 2024 reported that MedPro HCP search worked in the older experience but not in the new search experience. Disabling the new experience was the workaround reported by that customer.

This does not establish that the same workaround fixes the attendeeData save error.

 

Step 2 — Check MedPro attendee data mapping

Ask your MedPro integration administrator to compare a successful record with a failing record.

Field

Validation

External ID

Populated and correctly mapped

HCP first and last name

Valid values

Attendee type

Matches configured Concur type

NPI

Correct where applicable

Custom fields

Required fields mapped

Connector response

Contains expected attendee attributes

 

Do not change HCP identifiers or compliance classifications merely to bypass validation.

 

Step 3 — Verify Concur attendee configuration

  • In the appropriate Concur Expense administration area:
  • Open Attendees.
  • Verify the HCP attendee type is active for the relevant user group.
  • Review attendee form required fields.
  • Confirm that the MedPro connector is mapped to the correct attendee type.
  • Check for duplicate External IDs.
  • Retest using a previously failing HCP.

 

Step 4 — Escalate to SAP Concur Support

Because multiple connectors experienced the same JavaScript error, a shared Concur application defect is a credible possibility.

Ask SAP Concur Support to confirm whether the September 2024 defect has been corrected in your tenant and whether an applicable fix or known-issue reference exists.

 

Additional finding

A separate SAP Concur Community discussion, with replies through early 2026, described MedPro attendees appearing briefly and then disappearing from the expense attendee list. SAP Concur recommended opening a support case, and an employee indicated that the relevant mobile experience was optional at that time while longer-term solutions were being investigated.

 

Recommendation: First reproduce the error in desktop Concur and compare the supported attendee-search experiences. If both fail with the same attendeeData error, prioritize SAP Concur product support rather than immediately modifying MedPro master data.

 

Thanks & Regards

--

Samantha Prathikantam

SF_EC & ECP / SAP Concur Consultant

jenniferh
Occasional Member - Level 1

We are also having the same problem with the MedPro Connector. Is there any resolution to this?

pkinvesco
New Member - Level 3

We are having the same issue as of this morning with our Salesforce connector.  A user is trying to add a contact as an attendee and getting that error

anderste
Occasional Member - Level 2

We have escalated a ticket to Concur and understand their DEV team is aware of the issue and working on it.

Andras
SAP Concur Employee
SAP Concur Employee

Hi @jasone @athakur @anderste @pkinvesco 

 

Please accept our apologies for any inconveniences caused.

 

The issue has been fixed. Let me know if everything works correct. Thank you!


Best wishes,

Andras
SAP Concur

Did this response answer your question? Be sure to select “Accept as Solution” so your fellow community members can be helped by it as well.

athakur
Occasional Member - Level 3

Hello Andras,

 

We are still facing same issue. Just tested now.

I have a support ticket also open, but no update received about fix.

 

Ashish

anderste
Occasional Member - Level 2

thank you Andras! We are also still experiencing the error. 

Andras
SAP Concur Employee
SAP Concur Employee

Hi @athakur @anderste .

 

The fix was deployed 2 days ago for EU2, and it was promised to have it fixed yesterday by end of business day for US2.

 

Can you please check it now? Thank you


Best wishes,

Andras
SAP Concur

Did this response answer your question? Be sure to select “Accept as Solution” so your fellow community members can be helped by it as well.

athakur
Occasional Member - Level 3

Thanks Andras, issue is resolved. Attendee functionality is now restored.

 

Ashish

anderste
Occasional Member - Level 2

Thank you Andras. We have tested and it appears to now be functioning as expected. 

63378
Occasional Member - Level 2

We are experiencing this problem AGAIN ... since Tuesday ... are others having this recurring issue as well?

RaynerSurgical
New Member - Level 1

Our users are experiencing the above issue with the IQVIA OneKey connector since Mon/Tues.
A ticket has been created with Concur Support and they are directing me to the App provider. Had to do my own research concerning the outage to direct Concur Support on how to address the issue.....Concur Support over the past few years has become very unsupportive. Where assistance with an issue typically isn't provided. You are either sent an "article" or steps to fix the issue yourself.