Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Set new object property with dynamics 365 using Alexa CRM toolkit #40

Closed
MssefJian opened this issue Nov 6, 2017 · 7 comments
Closed

Comments

@MssefJian
Copy link

MssefJian commented Nov 6, 2017

I'm using AlexaCRM Toolkit for Dynamics 365, I added a new field for the entity lead with the name new_wordpressid so i can do the mapping with the lead created in wordoress and the lead in dynamics 365 , so when i want to create a new lead using the following code lines

$lead= $service->entity('lead'); $lead->firstname = 'john'; $lead->lastname= 'do'; $lead->new_wordpressid = '555'; $lead->create();

i get the following error :
Undefined property via __set() - lead does not support property: new_wordpressid in
/var/www/clients/client348/web348/web/wp-content/plugins/dynamics-amcham-crm/dynamics-amcham-crm.php on line 41 in
/var/www/clients/client348/web348/web/wp-content/plugins/integration-dynamics/vendor/alexacrm/php-crm-toolkit/src/Entity.php on line 261

Adding the new wordpress_id Causes an error. How can i set the wordpress_id Without having Any errors.
Thank you for your support and interaction

@georged
Copy link
Contributor

georged commented Nov 6, 2017

@MssefJian

  1. have you published customizations since you've added the field?
  2. What field type is new_wordpressid?

Thanks
George

@MssefJian
Copy link
Author

@georged the field type is Text, and yes i publish the customizations

@MssefJian
Copy link
Author

i really appreciate if someone could help me , i'm stuck with this error since 4 days

@georged
Copy link
Contributor

georged commented Nov 7, 2017

Can you upload a screenshot of the field definition. Form in CRM?

@MssefJian
Copy link
Author

amch

as i said before the field is a custom field

@wizardist
Copy link
Collaborator

Hi @MssefJian

Could you first update the package to the latest version? Run composer update alexacrm/php-crm-toolkit please and try again.

Also, do you employ any caching for MetadataCollection by any chance?

@MssefJian
Copy link
Author

MssefJian commented Nov 13, 2017

Hi @wizardist
thank you for your comment , i update the packege and i reconnect to dynamics crm , now it works perfectly . i think the problem was from the cache.

@georged georged closed this as completed Nov 13, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants