CRM Dynamics 2016 only allows to upload Excel and Word files as templates.
For the solution I am building I need to be able to upload a PDF so the users can choose it later on a custom dialog.
Is there a way this can be achieved? Maybe some add-on?
There are two third party products of note that are worth investigating and provide exactly this functionality.
DocumentsCorePack from MS-CRM Addons.
XperiDo from Invenso.
Related
If anyone knowledge about how to implement/create a digital signature for SharePoint 2013 and online document library?
Any answer will be highly appreciated. This is new for me.
Thanks!
Infowise is another option (I don't work for Infowise). I use them in custom training forms - the trainee and trainer both sign that the training has been completed.
I didn't realise it before, but the above link shows that it can also be used to sign off documents. (Though the OOTB Approval workflow can also be used for this purpose, of course).
[I work for DocuSign]
The DocuSign for SharePoint product supports true digital signatures for SharePoint documents.
I want to write a .NET application that will interface in realtime with Dynamics NAV 2009 and 2013. The application will have to read and update entities such as customers and stock items.
Using the provided webservices seem to be the best candidate as a point for integration, and I've tried some basic tests reading, updating and creating items using webservices based on Pages and a .net client.
Unfortunately, I am very new to Dynamics, and I have some questions that probably reflect that lack of experience.
First - webservices can expose either Page or Codeunits. Is Page the correct option to use for interfacing to say - create a customer?
Secondly - My understanding is that Dynamics NAV is rarely deployed without customisation. Would a typical customisation in NAV e.g an addition of a field involve changing a standard Page, and will this change then be reflected in the webservice definition?
You are right - given your requirements, webservices are probably the best option for interfacing with NAV.
Regarding your first question: page web services know how to handle concurrency, and, thanks to the way Visual Studio encapsulates them, expose rich types that you can interact with from your .NET code. All the basic CRUD operations can be carried out using the exposed methods. For a more detailed comparison between codeunit web services and page web services, please refer to http://msdn.microsoft.com/en-us/library/dd355398.aspx.
I think most developers choose not to publish the normal pages (the ones aimed at the NAV Windows Client; previously known as the Role Tailored Client), but instead, create separate, tweaked pages for publishing as a web service. But, if you prefer, I guess you could add your custom field to the standard page and publish that as a web service.
Hope this helps! Good luck! :)
I'm trying to modify and set alert templates on a SP (working on a copy of alerttemplates.xml), but I'd like to deploy them just on some specific sites, not the whole farm. Is this possible? I'm using SharePoint 2010 RTM.
Thanks
Changes take effect at the site collection level (aka top level site) and include all subsites in them
stsadm -o updatealerttempaltes
If you want more granular control you would have to look into IAlertNotifier, workflow or various 3rd party apps.
SO - Customise SharePoint Alerts
In SharePoint 2010, site templates (.stp files) are deprecated. Instead, solutions (.wsp files) are used to achieve the same effect, but also beyond that. Uploading .stp file and using it was straight forward in MOSS and WSS.
However, in SharePoint 2010, it is necessary to upload a solution and to activate it before using it. I need this functionality, and I also need it implemented through web services. Has anyone encountered something similar? Could anyone help? Thanks a lot.
OK, I've reached some people from the SharePoint design team at Microsoft and they have confirmed that there is no web service with a functionality to activate the solution. The upload of the solution should be done in a straight forward manner.
I unsure why you need to deploy a solution file using WebService. You can easily create a WSP Solution using this tool WSPBuilder and you can use Solution Installer to install the solution to the SharePoint farm. You can download the SharePoint installer's code and see what API to use to upload the solution to sharepoint.
I'm trying to upload documents to SharePoint using web services attaching custom metadata to the files. I've searched but have not found a good tutorial covering all these topics. Can anybody point me in the right direction?
Here's why I think I need to use web services:
I'm developing on XP and the Sharepoint object model is not remotable. This means any code which has "using Microsoft.Sharepoint" is out :-(
I'm looked into the CopyIntoItems web service but am having trouble implementing it myself. I was hoping for a clear tutorial. I've tried using the sample code from http://msdn.microsoft.com/en-us/library/copy.copy.copyintoitems.aspx , but I'm not sure what my sourceURL should be. Also, since I can't use "Microsoft.Sharepoint" references, I'm wondering what my Fields will look like? (Is this my metadata?) Also, I'm curious as to why only Website projects allow me to add a web service.
Once the file is "in" Sharepoint using that web service, I'll have to use another one to update custom columns, or metadata. Some of these are freeform text, but other must match entries in lists or lookups. I haven't found any information on this yet.
Thank you for your help!
Here is some code http://geek.hubkey.com/2007/10/upload-file-to-sharepoint-document.html
As for why it is that is the way because Microsoft wrote it that way :). Some people have written custom web services that combine them, http://www.sharepointblogs.com/ssa/archive/2006/11/30/wsuploadservice-web-service-for-uploading-documents-into-sharepoint.aspx
Using the built in web services you have to upload the file and upload CAML which contains the columns. Another option if you are using a MS-Office document is to make sure the author fills in the properties in the document then you can have those fields displayed in sharepoint.
Here is some stuff on the Sharepoint Designer - http://office.microsoft.com/en-us/sharepointdesigner/FX100487631033.aspx
Hope that helps a little.
You can link to the Sharepoint 2007 training from here: http://office.microsoft.com/en-us/training/HA102358581033.aspx
The designer I believe has a WS example in it.