alexacrm

Hi @markette

Yes, absolutely! Forms, views and entity record binding (documentation pending) are at you service.

Hi @Developper,

try checking the box to ignore certificate errors. Depending on where your WordPress installation is (e.g. we have similar reports for WordPress installations in Azure), connection to Dynamics 365 Online may throw invalid cartificate errors. We’re working with Microsoft trying to get to the bottom of the issue. In the meantime, ignoring certificate problems may solve the issue.

Thanks
AlexaCRM Support

@pierinux I appreciate the need for privacy hence the ask to contact us directly via email. We are adding some troubleshooting facilities to tackle exactly this type of errors but that would require additional logs being accessed by our support. Those logs would contain endpoint information so we would require your consent even when the facilities are available.

As a shot in a dark, try checking the box to ignore SSL errors – we’ve seen all sort of bizzare issues with 3rd party certificates

@Developper

can you please let us know the versions of the plugin, WordPress install and PHP in your environment.

Thanks
AlexaCRM

@pierinux it’s quite possible that the problem is more wide-spread than we think but we need some assistance from you, guys, to help us in nailing it down.

To start with, we need to know your org external URL – that will allow us to check that the wsdl returned by your servers is what we expect. Can you please email your org URL to [email protected] to help our troubleshooting? Note that we don’t need any credentials or any other information at this point.

Thanks
George

@sdmurthy,

at what point in time do you receive this error? Reason I’m asking is that we don’t have this specific error message in our plugin so it must be coming from the external system. Our plugin does not use and cannot use SSO with whatever system you’re using. At what point in time do you expect SSO to kick in?!

Thanks

@renysobin

What do you mean by fields being populated? Are you connecting the form to the existing record? Or you’re not seeing new custom fields in the layout?

• Have you published the form?
• Try flushing the metadata cache in the plugin settings (Regenerate Metadata Cache button)

Failing that, if you have any caching plugin on your site, try flushing that cache as well.

Thanks

Hi @rbshoretech,

I believe the issue has been resolved in the latest build. Can you please update the plugin and try again?

Thanks
AlexaCRM

Hi @deeganjx,

can you please send your organization url to [email protected], please?

Thanks
AlexaCRM

Hi

Please try to update the plugin and try again.

Hi @rbshoretech,

looks like wsdl coming back blank indicating that perhaps URL is incorrect. Can you please provide us with the organization URL you are using in settings. (Please email support if concerned about privacy)

Thanks
AlexaCRM

Hey @nkdesigns,

this error usually indicates that PHP version of your WordPress environment is lower than 5.4. We do indicate in the plugin description that this is the lowest version of PHP we support.

Note that version 5.3 had end-of-life over two years ago, so our recommendation would be to upgrade. If your WordPress is hosted by a third-party, you need to contact them about the upgrade.

HTH
@alexacrm

Hi @cprasad

Documentation is a priority. We’re working on it. You can definitely work with your CRM forms from WordPress. You can refer to the old docs for a while: https://docs-old.alexacrm.com/forms-views-and-pages/

—
Best regards.

Hi. Our plugin doesn’t support PHP 5.3. You need at least PHP 5.4 for this plugin to work. Please ask your hosting provider how to upgrade PHP to a newer version.

@alishoja, we’ve created a new enhancement request, you can track the progress on github