custom click to call implementation in mscrm 2013, currently dynamics crm 2013 built in support for Skype and lync. Is there any way I can override this behaviour so that call will be made from my telephony application. Is there customization support for this ?
You can't override the default behavior for phone fields that has Skype/Lync integration.
The alternative is to build a WebResource that will display the phone number and implement your click to call, or create a command button (ribbon) to handle the call.
Related
We just released our Office JS Add-In for Outlook. Our Add-In takes one or more emails and sends them to an external web service to upload as a case note attachment for our enterprise application. With the previous Visual Studio Tools for Office (VSTO) technology, we could invoke our Add-In with any number of emails selected so that many could be sent at one time. With the Office JS technology, if we select any more than 1 email, the Add-In button is not enabled and we can't invoke our Add-In. We have 12,000 customers using this tool using VSTO and they will report this as a bug for our Add-In given that the old technology works and the new technology does not. We would like this capability added for Office JS so our customers can do what they did using VSTO.
This is not possible today. We track Outlook add-in feature request on our user-voice page.
It looks like the feature you want has been requested by others already. Please upvote the existing request https://officespdev.uservoice.com/forums/224641-feature-requests-and-feedback/suggestions/11080962-allow-outlook-add-in-commands-to-be-used-on-select. Feature request on user-voice are considered when we go through our planning process.
I am developing an outlook addin using visual studio 2017 outlook web addin template.
I want to handle the event when the addin was first installed.
How can I get the installation event.I refered this link but its not giving me any event information for addin.
Office.initialize is used for determining when an add-in is launched and the runtime is ready. When the event is invoked, it means that all Office.js APIs are ready to use. There is no event for when add-ins are installed. If you are looking to create a "First-Run" Experience, you may use the RoamingSettings object to set some kind of mark if user went through your guide and doesn't want to see it any longer. This object will be available right after Office.initialize, so you can try to get this mark (key) and redirect to your app page(s) or your guide page(s) according.
I'm simply trying to enable tracing in System Settings -> Customization tab and the OK button does not work. There is a JavaScript error which say: "Object doesn't support property or method 'down'"
Has anybody encountered that and have possible workaround to this. I'm using Microsoft Dynamics CRM 2016 on-premise
which project use to create event receiver for sharepoint 2007 list - sequential workflow or state workflow? i'm using VS 2010
Neither.
Workflows are events which are run via the SharePoint Timer service and can be executed by any server in the farm.
An event receiver is essentially an event handler that will be executed either synchronously or asynchronously (depending on which event you're implementing) on the same server which handled the request that triggered the event receiver.
Visual Studio 2010 does not have much OOTB support for SharePoint 2007. You might consider installing the WSP Builder extensions (note that the proper download is not the recommended download - you'll need the 2010 BETA 1.4). They give new project types which include event receivers. Note though that there are some quirks with those project types but overall they are very helpful to getting the project set up correctly.
Be sure to read the documentation regarding the folder/file layout of your projects. If done correctly, you can use WSPBuilder to generate your WSPs for you.
A quick search revealed this blog post which might help get you started with regard to project structure. I'm sure there are many, many more references available. Happy coding!
Can someone give me a quick explanation of when I would use Visual Studio 2008 Outlook 2007 Ad-In project type? and how would that compare to developing a bunch of outlook macros directly in outlook?
Basically, I want to have some sort of application read email (with attachments) from a pop3 email box, do some filtering/editing/validation of the subject/sender/content and then if certain conditions are met, save the attachments to a local file, and then add an entry into an SQL server database table (i.e. date/sender/subject/message).
Seems there are at least 10 different ways to do this....so between an outlook macro and a VS Office Project, how do I pick?
I am not clear, if I create this solution as a Visual Studio outlook add-in, where does it run? Is it loaded into outlook, does it run as a separate process and communicates back and forth with outlook? if outlook is not running, does it start it?
An Outlook Add-on is a compiled component that uses the Outlook API to perform the tasks you need. A macro/VB script is an interpreted script that actually uses the same API. The add-on approach is better if you want to deploy your functionality.
When you work on an Outlook add-on in Visual Studio, you'll be creating a .NET component, which integrates into the Outlook application, which is written in C++ so uses COM. You'll have to be careful about managed/unmanaged types and releasing objects you retrieve from Outlook.
I have recently completed just such a tool, but I chose to use Add-in Express (http://www.add-in-express.com/). These guys provide a layer of abstraction over the [challenging] Outlook API and also provide some excellent support if you're stuck.
In my case, with Add-in Express, I "run" by setting Outlook as the application command to run, in the Project properties. Add-in Express sorts out the installation of the add-on within Outlook. So when I press "Run", Outlook starts and my add-in is displayed, which may be debugged in the normal fashion. I'm not sure how VSTO (Visual Studio Tools for Office) works in this respect - or at least, I can't remember.
This is an example of an outlook add-in..
Personally, I don't see macros distributable.