File System Import (Import Provider) - Revision history

Rpatton: // via Wikitext Extension for VSCode

2025-06-06T20:25:26Z

// via Wikitext Extension for VSCode

← Older revision		Revision as of 15:25, 6 June 2025
Line 47:		Line 47:

	=== Batch Creation ===		=== Batch Creation ===



			==== Folder Levels property ====

			The Folder Levels property under Batch Creation for a File System Import allows you to maintain the Windows' folder hierarchy in your Batch when the documents are imported into Grooper.

			The File System Import Provider can be used in many different places in Grooper (wherever you can configure an import). In this tutorial, we are going to instruct you how to use the File System Import Provider when creating a new Import on the Import Page.

			# Click the icon in the Context Toolbar to navigate to the Imports Page.
			# Click on the Add icon on the right side of the Context Toolbar.
			# Set the Description, Provider, and all Provider properties to your preferences for your import (see the [[#Basic Configuration]] section above for details on how to set that up).
			# Open the Folder Levels property editor by clicking the "..." icon to the right of the property.
			# Click the Add "+" icon at the top of the editor.
			# Change the Folder Level property to the folder level you want to keep when importing into Grooper. Add another to the list if desired by clicking the Add "+" icon.
			#* Consider the UNC Path of <code>\\OKCWGRO02\Imports and Exports\Imports\Documents to Import\001\Leases</code>. Ignore the network name and count the number of folders in the Path. Assign a number starting with number 1 to each folder.
			#** "Imports and Exports" would be 1.
			#** "Imports" would be 2.
			#** "Documents to Import" would be 3.
			#** "001" would be 4.
			#** "Leases" would be 5.
			#* If you wanted to keep the 001 and Leases folders in your Batch, you would need to set two Folder Levels to 4 and 5.
			# Click "OK" in the top right corner of the Folder Levels editor.
			# Click "Submit" at the top right of the Submit Import Job window to submit the job.
			# When you look at your imported Batch, the Folder Levels in your Batch should be the same folders you specified when configuring the import.

			[https://app.supademo.com/demo/cmbkutcey00hgya0ig1ilssig Click here for an interactive walkthrough]

Rpatton: // via Wikitext Extension for VSCode

2025-06-06T14:06:05Z

// via Wikitext Extension for VSCode

← Older revision		Revision as of 09:06, 6 June 2025
Line 14:		Line 14:
	== About ==		== About ==

	The File System Import Import Provider is considered a Legacy Import Provider. It is recommended in all current and future versions of Grooper to configure your Projects using ~~either~~ [[Import Descendants]] or [[Import Query Results]] instead. It is still an option in Grooper primarily for Projects orginally created in previous versions of Grooper that have been updated to newer versions.		The File System Import Import Provider is considered a Legacy [[Import Provider]]. It is recommended in all current and future versions of Grooper to configure your Projects using a [[CMIS Connection]] set to [[NTFS]] and an [[Import Descendants]] or [[Import Query Results]] Import Provider instead. It is still an option in Grooper primarily for Projects orginally created in previous versions of Grooper that have been updated to newer versions.

			== How To ==

			Remember, this Provider is a Legacy Provider and should only really be used when updating a Project that was created in a previous version of Grooper that is already set up with File System Import. For those that need to update their Provider, this is how File System Import works.

			=== Basic Configuration ===

			This is a Basic Configuration guide for File System Import. To make edits to what the Batch is named and how to assign the Batch to a Batch Process on import, see the [[#Batch Creation]] section of this article.

			# Click over to the Imports Page in Grooper.
			# Click the Add "+" icon on the right side of the Context Toolbar.
			# When the Submit Import Job window appears, enter in a Description for your Import.
			#* This is the name of your Import Job, not the name of the Batch that will be created.
			# Set the Provider property to File System Import. Click the hamburger icon "☰" to access the drop down.
			# Open the Provider sub properties and insert the UNC Path to the folder you want to import from into the Base Directory property.
			# Decide if you want to Include Subfolders in your import and set to True or False accordingly.
			#* If set to false, it will only import documents in the immediate folder, ignoring any documents in subfolders.
			# Required or Ignore Attributes properties will let you specify attributes of documents you want to bring in or you want to exclude from the import.
			# Allowed File Extensions and Excluded File Extensions allow you to specify what file extensions to import.
			# Exclusion Patterns allow you to use regex to determine certain files not to import.
			# If you set the maximum file size, no documents larger than this will be imported.
			# Ignore Unknown File Types when set to True will not import any documents that have file types Windows does not recognize.
			# The File Disposition property determines what happens to the documents when they are imported.
			#* The Delete option for the File Disposition will not appear if you are performing a Sparse Import.
			# Decide whether you want a Sparse Import and set to True or False accordingly.
			# click "Submit".

			You should now have imported documents in your Test Folder under your Batches folder in the design page. They should be located in a folder called "Imported Batches".

			[https://app.supademo.com/demo/cmbjrju54013e080i4tzhk3tz Click here for an interactive walkthrough]

			=== Batch Creation ===

Rpatton: // via Wikitext Extension for VSCode

2025-06-05T16:42:21Z

// via Wikitext Extension for VSCode

← Older revision		Revision as of 11:42, 5 June 2025
Line 13:		Line 13:

	== About ==		== About ==

			The File System Import Import Provider is considered a Legacy Import Provider. It is recommended in all current and future versions of Grooper to configure your Projects using either [[Import Descendants]] or [[Import Query Results]] instead. It is still an option in Grooper primarily for Projects orginally created in previous versions of Grooper that have been updated to newer versions.

Rpatton: Created page with "{{AutoVersion}} {|class="wip-box" | '''WIP''' | This article is a work-in-progress or created as a placeholder for testing purposes. This article is subject to change and/or expansion. It may be incomplete, inaccurate, or stop abruptly. This tag will be removed upon draft completion. |}
{{#lst:Glossary|File System Import}}
== About =="

2025-06-05T16:31:48Z

Created page with "{{AutoVersion}} {|class="wip-box" | '''WIP''' | This article is a work-in-progress or created as a placeholder for testing purposes. This article is subject to change and/or expansion. It may be incomplete, inaccurate, or stop abruptly. This tag will be removed upon draft completion. |} <blockquote>{{#lst:Glossary|File System Import}}</blockquote> == About =="

New page

{{AutoVersion}}

{|class="wip-box"
|
'''WIP'''
|
This article is a work-in-progress or created as a placeholder for testing purposes. This article is subject to change and/or expansion. It may be incomplete, inaccurate, or stop abruptly.

This tag will be removed upon draft completion.
|}

<blockquote>{{#lst:Glossary|File System Import}}</blockquote>

== About ==