Comments
It has been still for a while, but hopefully I can add some life to this bright idea. In general, DAMS processes have little transparency.I'm observing indexes that DAMS has created. Some of them make sense, but some are ridiculous. I'm seeing one with 14 key columns and 29 included. This is breaking recommendations for good index design and reduces trust to DAMS as such. Seeing how and if indexes are used, would allow us as a partner make better design decisions, work on user training and have better dialog with MS.
I can only agree. It is a shame that the idea was submitted in 2017 is currently relatively high voted and not considered for evaluation. Also some other ideas in different areas surpass 130 votes and have been under review for almost a year.It is very sad to see, that this is not going forwards at the moment
We have a further requirement.Currently only contacts that have an e-Mail address can be synched.It would be much better, if any personal contact could be synced,Some people use Exchange Contacts on their mobile devices for calling them.I checked the graph API and was able to create a contact without mail address there without any problem.https://learn.microsoft.com/en-us/graph/api/user-post-contacts?view=graph-rest-1.0&tabs=httpWe would simple need to store the Microsoft Graph API in BC to map this contact to a BC Contact. This should be possible with a simple 1-n table for Contacts to Outlook Contacts.