alexacrm
Forum Replies Created
-
Forum: Plugins
In reply to: [Dynamics 365 Integration] Dynamics 365 Connection Setup: Critical ErrorLooks like the error is caused by lack of permissions for the logger to open file for read/write. By default it opens it in upload folder so permissions would need to be chacked on that one. But yes, Dataverse Integration plugin is definitely the one to use.
Forum: Plugins
In reply to: [Dynamics 365 Integration] Moving to TWIG@jenn0014 couple things to try
- Your instance seems to be disconnected from CRM and running on cached information. Perhaps the secret has expired. Reconnect your instance.
- Remove the first form so that you have only the second one?
- Do you have tabs or hidden sections on the form in CRM? Generally we recommend to use quick view form type – no script and less chance to get unsupported elements or hidden tabs.
Forum: Plugins
In reply to: [Dynamics 365 Integration] Moving to TWIGyou can start by simply replicating your shortcode but using twig instead. The most substantial change is from text to twig objects to describe the parameters.
[msdyncrm_twig]
{% form entity="lead" name="property" mode="create" captcha="true" redirect="http://www.stepproperty.co.uk/thank-you/" default={"leadsourcecode":100000008, "new_enquirytype":100000001, "new_propertytype":100000000} %}{% endform %}
[/msdyncrm_twig]Make sure your recaptcha is v3, as v2 is way too easy to break.
Hope it helps
- This reply was modified 1 year, 4 months ago by alexacrm.
Forum: Plugins
In reply to: [DataPress (Dataverse Integration)] Error while executing a CRM action@siddiquemahsud toolkit is included as part of the plugin. We handle connection, logging, caching. You can use it directly using
ConnectionService, for example:$webapi = ConnectionService::instance()->getClient();
$webapi->RetrieveByReference(...);Forum: Plugins
In reply to: [DataPress (Dataverse Integration)] Error while executing a CRM actionwhy are you using a custom action to delete a record instead of delete method from the toolkit? But if you want to create an
EntityReference, correct namespace is\AlexaCRM\Xrm:$ref = new \AlexaCRM\Xrem\EntityReference( $entity, $id);Forum: Plugins
In reply to: [Dynamics 365 Integration] Deprecated function strptime()This is part of the toolkit and will be updated at some point followed by a maintenance plugin release. It’s business critical as it’s only a deprecation notice and we don’t have any specific timeline to share but hope to get it done soon.
@cwcj if this is native N:N relationship then it would need to use Associate message, simple update won’t work. We have
integration-cds/forms/submit-successhook (see Hooks Reference | DataPress (alexacrm.com)). You’d need to Associate Web API method yourself (we provide the connection)Forum: Plugins
In reply to: [DataPress (Dataverse Integration)] Conflict with Filebird Prothanks for reporting the issue. The error is caused by the order in which jQuery libraries are loaded. This is something that we don’t control. We do load our copy of jQuery by the book and in the situations like this it’d be up to Filebird to resolve the conflict since they need jQuery UI in addition to the standard jQuery.
Best regards,
AlexaCRM Support@chrisjdahl thanks for raising the issue. We are aware of this regression and it’s going to be fixed in the next build in a day or two.
The second issue (with the download error) should be already resolved
Thank you
AlexaCRMForum: Plugins
In reply to: [Dynamics 365 Integration] Call to undefined function ASDK()Is plugin itself connected and working?
Tbh, this is a very left of field scenario and if that approach works, all the powers to you!
Glad so see it resolved. If you happy with the plugin and have a spare minute or two, we’d appreciate a review.
Thank you,
George
AlexaCRMLet me see if I understand it correctly. If you want to keep the HTML field empty while the actual Dataverse column has a value and then treat no input as “leave the field alone” then off top of my head, you can use two approaches:
- Keep collection of values “on a side” and on form submit inject those values instead of blanks. Or even try removing the values using FormData object.
- Create additional columns in Dataverse that would take the values entered by the user and then have a Power Automate flow on update that would copy the values over to the actual columns but only if they are not blanks
HTH
@chrisjdahl can you please describe the scenario? Are you editing an existing record or creating a new one? I’m trying to understand the context when we shouldn’t send empty fields as nulls
for multistep forms we recommend using Gravity Forms. Since they are a form plugin dedicated to robust form processing, the functionality on offer is much more sophisticated. Note that you’d need a premium version of our plugin to integrate with Gravity Forms.
Thank you,
AlexaCRM SupportForum: Plugins
In reply to: [Dynamics 365 Integration] Enabling IFD (Internet Facing Deployment)Internet Facing Deployment is the configuration for Dynamics 365 On-Premises installations, as per documentation. It does not apply if you have a Dynamics 365 online instance in your Microsoft 365 tenant.