File System Import (Import Provider): Difference between revisions
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 ==" |
// via Wikitext Extension for VSCode |
||
| 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. | |||
Revision as of 11:42, 5 June 2025
|
This article is about the current version of Grooper. Note that some content may still need to be updated. |
| 2025 |
|
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. |
File System Import refers to a Legacy Import Provider used to import documents directly from your Windows File System into Grooper.
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.