KB: Linking vs Copying Documents - Revision history

Dina at 12:35, 8 July 2020

2020-07-08T12:35:10Z

← Older revision		Revision as of 12:35, 8 July 2020
Line 1:		Line 1:
	==Copying Files==		==Copying Files==
	The ~~CommitCRM~~ system allows users to import a single document into the ~~CommitCRM~~ documents folder, and create a document entry in the ~~CommitCRM~~ database. This document can be linked to your '''Accounts/Tickets/Contracts/Assets/Opportunities''' which are logged in ~~CommitCRM~~, so that they can be easily accessed via the software application or the ~~CommitCRM~~ Web Interface.		The RangerMSP system allows users to import a single document into the RangerMSP documents folder, and create a document entry in the RangerMSP database. This document can be linked to your '''Accounts/Tickets/Contracts/Assets/Opportunities''' which are logged in RangerMSP, so that they can be easily accessed via the software application or the RangerMSP Web Interface.


	===Benefits of Copying===		===Benefits of Copying===
	*When copying files into the ~~CommitCRM~~ documents folder, you are enabling other users to view the file, based only on ~~CommitCRM~~ security permissions, assuming the documents folder is accessible to '''Everyone''' or '''Domain.com''' in windows security.		*When copying files into the RangerMSP documents folder, you are enabling other users to view the file, based only on RangerMSP security permissions, assuming the documents folder is accessible to '''Everyone''' or '''Domain.com''' in windows security.
	*When using this method, the documents are all filed in a consolidated documents store, where they are divided on the account level, which ultimately makes the documents backup process much easier to perform.		*When using this method, the documents are all filed in a consolidated documents store, where they are divided on the account level, which ultimately makes the documents backup process much easier to perform.


	==Linking Files==		==Linking Files==
	When importing documents into ~~CommitCRM~~, the second method of import is '''linking the original files into the ~~CommitCRM~~ database''' while leaving it only on the original path. This method allows the importing user to keep his own systems permissions in effect on the imported file/s.		When importing documents into RangerMSP, the second method of import is '''linking the original files into the RangerMSP database''' while leaving it only on the original path. This method allows the importing user to keep his own systems permissions in effect on the imported file/s.

	When you import a whole folder into ~~CommitCRM~~, you aren't actually '''copying the files''' from the local computer to the ~~CommitCRM~~ server, you are only '''linking the files''' from there current location into the ~~CommitCRM~~ documents database, as mentioned when linking single files into ~~CommitCRM~~.		When you import a whole folder into RangerMSP, you aren't actually '''copying the files''' from the local computer to the RangerMSP server, you are only '''linking the files''' from there current location into the RangerMSP documents database, as mentioned when linking single files into RangerMSP.

	If you've imported a document folder into ~~CommitCRM~~, and other computers than the one which you imported the folder from cannot '''view/edit''' these files, by telling you "file does not exist or cannot be accessed ", this would be the reason.		If you've imported a document folder into RangerMSP, and other computers than the one which you imported the folder from cannot '''view/edit''' these files, by telling you "file does not exist or cannot be accessed ", this would be the reason.

	In order to test this theory, you can try to use ~~CommitCRM~~ to access these documents from the computer you've imported from, and if you're successful, then the problem is in the security permissions for the file, on the computer they are linked from.		In order to test this theory, you can try to use RangerMSP to access these documents from the computer you've imported from, and if you're successful, then the problem is in the security permissions for the file, on the computer they are linked from.


	===Benefits of Linking===		===Benefits of Linking===
	*When linking files into ~~CommitCRM~~, the files retain their Windows Security settings, and can be adjusted by any administrative user on the machine hosting the document.<br>		*When linking files into RangerMSP, the files retain their Windows Security settings, and can be adjusted by any administrative user on the machine hosting the document.<br>

	'''For more information regarding Importing Multiple Documents & Windows Security Settings, [[Documents#Importing_Existing_Documents\|please click here]].'''		'''For more information regarding Importing Multiple Documents & Windows Security Settings, [[Documents#Importing_Existing_Documents\|please click here]].'''

Dina: Dina moved page KB: Linking vs Copying Documents into CommitCRM to KB: Linking vs Copying Documents

2020-03-22T14:08:15Z

Dina moved page KB: Linking vs Copying Documents into CommitCRM to KB: Linking vs Copying Documents

← Older revision	Revision as of 14:08, 22 March 2020
(No difference)

Robert at 10:49, 1 September 2013

2013-09-01T10:49:53Z

← Older revision		Revision as of 10:49, 1 September 2013
Line 1:		Line 1:
	==Copying Files==		==Copying Files==
	The CommitCRM system allows users to import a single document into the CommitCRM documents folder, and create a document entry in the CommitCRM database. This document can be linked to your '''Accounts/Tickets/Contracts/Assets/Opportunities''' which are logged in CommitCRM, so that they can be easily accessed via the software application or the ~~Commit~~ Web Interface.		The CommitCRM system allows users to import a single document into the CommitCRM documents folder, and create a document entry in the CommitCRM database. This document can be linked to your '''Accounts/Tickets/Contracts/Assets/Opportunities''' which are logged in CommitCRM, so that they can be easily accessed via the software application or the CommitCRM Web Interface.

Sheli: /* See also */

2009-11-23T16:19:59Z

Reno at 20:03, 17 November 2009

2009-11-17T20:03:28Z

← Older revision		Revision as of 20:03, 17 November 2009
Line 1:		Line 1:
	==~~Introduction~~==		==Copying Files==
	The CommitCRM system allows users to import a single document ~~or document folder~~ into the CommitCRM ~~database~~, and ~~have it~~ linked to your '''Accounts/Tickets/Contracts/Assets/Opportunities''', so that they can be easily accessed via the software application or the Commit Web Interface.		The CommitCRM system allows users to import a single document into the CommitCRM documents folder, and create a document entry in the CommitCRM database. This document can be linked to your '''Accounts/Tickets/Contracts/Assets/Opportunities''' which are logged in CommitCRM, so that they can be easily accessed via the software application or the Commit Web Interface.

	~~Sometimes, if this option has not been correctly set, there may be issues accessing the document.~~

			===Benefits of Copying===
			*When copying files into the CommitCRM documents folder, you are enabling other users to view the file, based only on CommitCRM security permissions, assuming the documents folder is accessible to '''Everyone''' or '''Domain.com''' in windows security.
			*When using this method, the documents are all filed in a consolidated documents store, where they are divided on the account level, which ultimately makes the documents backup process much easier to perform.

	==~~Solution~~==
	When ~~you import a whole folder~~ into CommitCRM, ~~you aren~~'~~t actually~~ ''~~'copying~~ the files~~''' from the local computer to~~ the CommitCRM ~~server, you are only~~ '''~~linking~~ the ~~files''' from there current location into~~ the ~~CommitCRM documents database~~.		==Linking Files==
			When importing documents into CommitCRM, the second method of import is '''linking the original files into the CommitCRM database''' while leaving it only on the original path. This method allows the importing user to keep his own systems permissions in effect on the imported file/s.

	If you~~'ve imported~~ a ~~document~~ folder into CommitCRM, ~~and other computers than the one which~~ you ~~imported~~ the ~~folder from cannot~~ '''~~view/edit~~''' ~~these~~ files~~, by telling you "file does not exist or cannot be accessed ", then here~~'s the ~~explanation:~~		When you import a whole folder into CommitCRM, you aren't actually '''copying the files''' from the local computer to the CommitCRM server, you are only '''linking the files''' from there current location into the CommitCRM documents database, as mentioned when linking single files into CommitCRM.

	In order to test this theory, you can try to use CommitCRM to access these documents from the computer you've imported from.		If you've imported a document folder into CommitCRM, and other computers than the one which you imported the folder from cannot '''view/edit''' these files, by telling you "file does not exist or cannot be accessed ", this would be the reason.

			In order to test this theory, you can try to use CommitCRM to access these documents from the computer you've imported from, and if you're successful, then the problem is in the security permissions for the file, on the computer they are linked from.


			===Benefits of Linking===
			*When linking files into CommitCRM, the files retain their Windows Security settings, and can be adjusted by any administrative user on the machine hosting the document.<br>

	'''For more information regarding Importing Multiple Documents & Windows Security Settings, [[Documents#Importing_Existing_Documents\|please click here]].'''		'''For more information regarding Importing Multiple Documents & Windows Security Settings, [[Documents#Importing_Existing_Documents\|please click here]].'''
Line 16:		Line 25:

	==See also==		==See also==
	*[[Documents#Importing_Existing_Documents\|~~please click here~~]]		*[[Documents#Importing_Existing_Documents\|Importing Existing Documents]]

	[[Category:KB\|Documents]]		[[Category:KB\|Documents]]

Reno: Created page with '==Introduction== The CommitCRM system allows users to import a single document or document folder into the CommitCRM database, and have it linked to your '''Accounts/Tickets/Cont…'

2009-11-17T19:22:54Z

Created page with '==Introduction== The CommitCRM system allows users to import a single document or document folder into the CommitCRM database, and have it linked to your '''Accounts/Tickets/Cont…'

New page

==Introduction==
The CommitCRM system allows users to import a single document or document folder into the CommitCRM database, and have it linked to your '''Accounts/Tickets/Contracts/Assets/Opportunities''', so that they can be easily accessed via the software application or the Commit Web Interface.

Sometimes, if this option has not been correctly set, there may be issues accessing the document.

==Solution==
When you import a whole folder into CommitCRM, you aren't actually '''copying the files''' from the local computer to the CommitCRM server, you are only '''linking the files''' from there current location into the CommitCRM documents database.

If you've imported a document folder into CommitCRM, and other computers than the one which you imported the folder from cannot '''view/edit''' these files, by telling you "file does not exist or cannot be accessed ", then here's the explanation:

In order to test this theory, you can try to use CommitCRM to access these documents from the computer you've imported from.

'''For more information regarding Importing Multiple Documents & Windows Security Settings, [[Documents#Importing_Existing_Documents|please click here]].'''

==See also==
*[[Documents#Importing_Existing_Documents|please click here]]

[[Category:KB|Documents]]

← Older revision		Revision as of 16:19, 23 November 2009
Line 26:		Line 26:
	==See also==		==See also==
	*[[Documents#Importing_Existing_Documents\|Importing Existing Documents]]		*[[Documents#Importing_Existing_Documents\|Importing Existing Documents]]
			*[[Documents]]

	[[Category:KB\|Documents]]		[[Category:KB\|Documents]]