alexacrm

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-success hook (see Hooks Reference | DataPress (alexacrm.com)). You’d need to Associate Web API method yourself (we provide the connection)

@neylk

thanks 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
AlexaCRM

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
AlexaCRM

Let 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:

1. 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.
2. 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

@chrisjdahl,

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 Support

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.

Hi Menno,

unfortunately, we can’t just update packages as it will break the functionality for PHP 7.4. We appreciate that 7.4 is no longer supported but we have users still running those environments. We’re working on the release that would allow us to freeze anything below 8.2 and then we’ll be able to upgrade.

Having said that, I would strongly recommend switching to the Dataverse plugin instead. I believe we have the same issue right now, but we prioritise the updates for that plugin. It is a superset in terms of functionality, based on Web API, and has support for the latest Dataverse features and data types.

Thank you,
AlexaCRM Support

Zach,

if you’re using twig forms I would strongly recommend using Dataverse plugin instead. The only change you’d need is replace [msdyncrm_twig] with [icds_twig] shortcode.

You can find a sample how to display lookups using dropdown control here: Using lookups in the free plugin version | DataPress (alexacrm.com)

Thank you,
AlexaCRM Support

Hi @ztwoods

the page size in lookups is set to 10 and, unfortunately, there is no setting to change it. You can modify it directly in the LookupDialog.php file but considering limited number of entries in your case, I would suggest using dropdown instead.

As far as the pagination buttons are concerned, you can always adjust crm-lookup-popup-xxx styles to match your page style (in your case you have additional padding set on table rows pushing the height of the container).

Thank you,
AlexaCRM Support

Ah, sorry, forgot to add that in addition to the column name as above, the values need to be one of the following:

• Serialised EntityReference in the format { "LogicalName": "contact", "Id": "00000000-0000-0000-0000-000000000000" }. Easiest way is to use to_entity_reference filter
• Simplified old-style syntax of table:guid as a value

Examples

<select?name="ud_countryid">
   {%?for?ud_country?in?countries.results.entities?%}
      <option?value="{{?ud_country?| to_entity_reference }}">{{ud_country.ud_name?}}</option>
   {%?endfor?%}
</select>

OR, simplified syntax

<select?name="ud_countryid">
   {%?for?ud_country?in?countries.results.entities?%}
      <option?value="ud_country:{{ ud_country.ud_countryid }}">{{ud_country.ud_name?}}</option>
   {%?endfor?%}
</select>

@kimineko

try the column logical name <select?name="ud_countryid"> and let us know if it worked.

Thanks
AlexaCRM Support