We’re looking at implementing the Kinetic/Sharepoint integration in a compressed timeframe and I’d like to avoid making any bad decisions that will come back to haunt me.
Our current attachment are “link” type. One business unit is storing the attachments on network storage. The other business unit is copying links from Sharepoint and pasting those links into the attachment paths.
We have a need to standardize across business units and move to Sharepoint storage for all new attachments. We haven’t determined whether we will migrate the existing network stored attachments to Sharepoint.
The Kinetic/Sharepoint integration should make a smoother process for getting the new files into Sharepoint and attached to orders, parts, jobs, etc.
It seems that a recent change to the integration is the ability to use multiple document libraries controlled by Document type. Has anyone found this beneficial? What was your use case?
I’m intrigued with getting metadata populated in Sharepoint from Kinetic. Some posts and documentation indicate that the values from the metadata can only come from the table associated with the attachment. However, @klincecum has disputed that. Care to share?
I infer that the Kinetic integration pulls a file link that is based on the filename and path. @Mark_Wonsil mentioned in a post that he’s using links with a unique document ID. Is there an automated path to this when the user wants to upload the file from Kinetic?
Has anyone implemented the integration in a way that you would not recommend?
Thanks!