Outlook integration - location supports also field name cLocation

[SylviaM]

As mentioned in the documentation of the Outlook integration on https://docs.espocrm.com/extensions/...tion/calendar/

If your Espo entity type has a custom Varchar field named location, it will be synced with Outlook Calendar. As of v1.4.0.

My problem occured when I added this varchar field to the meeting entity. As meetings are a standard entity it was named cLocation.


Now the location isn't synched to my Outlook.

Please add that the field can also be named cLocation to support it for standard entities.

[heint]

Greetings,SylviaM

What version of Espo and Outlook are you using? I've just checked it on my server and it's working fine

[SylviaM]

Hi,
thanks for the response.
Espo is Version 9.2.7
Outlook is part of Microsoft 365 for Enterprise (Microsoft® Outlook® für Microsoft 365 MSO (Version 2508 Build 16.0.19127.20484) 64 Bit))

[heint]

Have your Meeting records been synchronized successfully before? And how does it behave now? When you fill up the "Location" field of the Meeting on the Espo side, does this record sync to Outlook at all or just with the "Location" field empty on the Outlook side?

Could you please share (you can change the actual location for testing value) what kind of data you are using in this "Location" field? Is it a simple string?

As a first preventive action, you can reconnect your Outlook account at {user} -> External Accounts (at the top right corner) -> Outlook in incognito mode to prevent any caching issues, which are quite usual for Outlook.

[SylviaM]

Hi,
for test purposes I created a new meeting with a location (address is a public airport)
The meeting itself synchs just fine. But the location is empty. Our sales reps need this particular feature for navigation apps in their cars.

We use an Exchange server in the Microsoft 365 cloud and the German version of everything. I hope that doesn't make a difference but I wanted to mention it.


Again, thanks for the help.

[heint]

Can your show details of the "Adresse" field? What type of the field is this? I'm not really sure what this small icon inside this field is doing.

Also do you have any customization (potential logic that fills up fields automatically) for any of the adress fields?

[SylviaM]

There is no customization yet that fills the location field. There is no actual connection between those fields of the address and the cLocation field. I wrote/copied it manually into the cLocation.
The comes from a Google Map extension "Ebla Map Plus". With a click on it you get your current position as an address.

I'm writing a story (I'm the Product owner) to fill the address field from the address of the parent, then fill the cLocation field by concatenating the address values and finally send it over to Outlook. So it's a new feature to transfer the address to Outlook but the Outlook integration is running for a couple of months now.

We have the following extensions installed.

The OpenAPI Generator is written by our developers and just creates the OpenAPI documentation that other software needs to use the EspoCRM API.

[heint]

Edited: Before the steps below, please enable debug-mode first for your instance with the following steps:

- Enable Debug mode: https://docs.espocrm.com/administrat...ng/#debug-mode.
- Do all the synchronization tests.
- Provide the EspoCRM error log. EspoCRM log files are located in the {ESPO_ROOT}/data/logs/ directory. Most errors are logged there.

(If you don't want to share private logs publicly, you can create a case from your custom portal so only support team will handle it.)

Main part:

Have you tried to disable/uninstall custom extensions related to the map location? I would strongly recommend doing it, at least for testing purposes, and seeing if the issue persists.

After temporary deinstallation, don't forget to remove corresponding fields from the layout manager of the Meeting entity before testing.

If disabling map location-related extensions won't help, try to uninstall any other custom add-ons as well.

[Kharg]

The issue is clearly that cLocation has not been mapped to be used as a valid field for the integration extensions.


I once reported this in https://github.com/espocrm/espocrm/i...ent-2126929172 but apparently it was not taken care of.

Your best bet is to open a ticket in the official Portal for extensions and report this issue there or to disable the c prefix (customPrefixDisabled set to true) temporarily, create a normal Location field and then enable the C prefix once again.

[yuri]

> apparently it was not taken care of.

We've been supporting the 'cLocation' field in Google Integration as well, for a few years.

[Kharg]

Thank you for stepping in to clarify Yuri, much appreciated.

I supposed that it was not mapped as I did not receive a reply about it.

I am sorry for being wrong

[yuri]

It's fine. BTW it's our support handles this topic. Creating a case in the customer portal usually is not necessary as the same people will handle the duplicate issue.