Unanswered

Using canvas app to create new case in Dynamics 365 - customerid is missing and required

(0) Share

Report

Posted on by v-saperr Microsoft Employee

I am trying to create a test app that can create a new Case record in our Dynamics 365 instance by submitting a form to the entity to create a new record. I manually created a pair of test records from within Dynamics to reference, but cannot seem to add a new one from within a powerapp.

I have inputs for all the required fields except the customer field which doesn't auto populate and even if manually added does not function correctly.

If the form is connected via CDS it creates a blank customer card in the form and even if a control is added (for instance a combo box that shows the customerid_value) any attempts to submit the form result in the error "customerid is missing and required".

If it's connected via the old Dynamics connector it auto loads a text input box for customer, but even if a matching ID is input any attempts to submit the form result in an error "a value must be provided for the item".

Surely I must be missing something simple to fix this.... what's going wrong and how do I make this work?

Connected via CDS

Connected via Dynamics connector

Thank you,

-Sarah

Categories:

Building Power Apps

ConnectorError.PNG

NewCaseError.PNG

I have the same question (0)

All responses (6)

Answers (0)

v-monli-msft on at

Like (0)

Report

Hi @v-saperr ，

Check on the Update property of this customer id data card.

Regards,

Mona

Was this reply helpful? Yes No
v-saperr Microsoft Employee on at

Like (0)

Report

Hi Mona,

First off thanks for looking into this.
The dynamics connector based version of the form populates Update as: DataCardValue7.Text and has a card key. The DataCard has a Parent.Default source for its data.

The CDS connected version of the form doesn't have anything since a control has to be added to the customer card, but if I add a text input or other control type, combobox etc. the Update property is initially blank. If I try to manually set Update to [control].text or [control].selected or whatever, then it pops up an "expected polymorphic value" error.

I've looked into the documentation on polymorphic values and customer lookup but it was confusing on how this might apply to the Case entity since I don't think I understand how powerapps and dynamics are trying to interact with each other and that this might be part of the problem.

Does the form need to retrieve already existing data from the Customer field of the case entity or pull it from a different (accounts/contact) entity? Is the form submission supposed to feed a matching (or new value) to the customer field or to either the account/contact entity instead? Does it need both, to be looked up from one source and re-fed back? Or something else entirely?

It's also difficult for me to visual how the Accounts/Contact entities relate to the Customer field as nested inside the Case entity - does setting a value in of those entities result in a value in the Customer field? Is the reverse true?

I feel like if I understood the conceptual mechanic of how the information is supposed to flow between these things then I could figure out what step in the process is broken and/or why it doesn't work, but pretend I'm five and need a handhold to cross the street.

Customer data card

-Sarah

Was this reply helpful? Yes No
v-saperr Microsoft Employee on at

Like (0)

Report

Hi Mona,

Firstly, thanks for taking a look into this.

The update card on the old dynamics connector shows Update as: DataCardValue7.Text and that card value has a key and DataCardValue7's default property is Parent.Default but on submit for the form it bounces back a nonspecific "a value must be provide for item" error that I assume refers to the customer field, but if I give it a value, even a pre-existing Customer GUID it still says the same thing so I'm not certain what value from where it's asking for.

The CDS connected version of the customer card's update property is blank since it doesn't populate a control at all. If I manually add a control like either text input or combo box etc. and set update to [control].text or [control].selected or whatever, then it comes back with a "expected polymorphic values" error.

I looked into the documentation on polymorphic values and lookup, but it was confusing on how this would apply specifically to the Customer field inside the Case entity. I've been able to create form submissions for other entities in the dynamics instance, but this one seems more complicated. If I understood more about how powerapps and dynamics are supposed to interact I think I could figure out what I'm doing wrong.

Does the form need to pull information (like into a gallery?) from existing information in the Customer field of the Case entity? Is the form submission supposed to provide matching (or new?) data to the customer field inside the case entity? Does it need to look up and re-feed the information from one entity (Accounts/Contacts/Case) to another? Something else? None of the above?

For anyone with insights into this, please pretend I'm five and need a handhold to get across the street of the Abstract Concept that is entity manipulation.

Thanks,

-Sarah

Was this reply helpful? Yes No
antoniawolf 2 on at

Like (0)

Report

Did you ever get a solution for this? I'm running into the same issue. Can't create a case because the customer and owner fields are required but as they are polymorphic, not sure how to set them up.

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report

The "Customer" Field is a special little beast. It can pivot and be either a CONTACT or an ACCOUNT and as such it is one of those edge cases. You might consider showing the Account and Contact fields and then using a flow to take that data to populate customer.

Was this reply helpful? Yes No
v-saperr Microsoft Employee on at

Like (0)

Report

I did figure out a work around using a combo box inserted into the Customer Card where the Update property for the card is set to (comboboxname).Selected and then tied the combo box Items property to Contacts (it should work if also tied to accounts) with the Display and Search properties/fields as ["fullname"] then had the results of a search box elsewhere modify that combo box's default to my selected search criteria.

It's messy, but it worked.

Was this reply helpful? Yes No