Box (CMIS Binding) - Revision history

Dgreenwood: /* Box CMISQL Query limitations */

2026-04-20T13:58:30Z

Box CMISQL Query limitations

← Older revision		Revision as of 08:58, 20 April 2026
Line 650:		Line 650:
	Box has some documented limitations in its CMIS implementation in general. In most cases, Grooper is able to circumvent these issues, but not in all cases. Grooper is only able to return what Box gives us when executing a CMISQL query.		Box has some documented limitations in its CMIS implementation in general. In most cases, Grooper is able to circumvent these issues, but not in all cases. Grooper is only able to return what Box gives us when executing a CMISQL query.
	* Documents are not immediately queryable after their metadata templates have been edited in Box. If you have just added/edited fields in a Box document's metadata template, there is some lag time between when Grooper can query that data. You may need to wait several hours before a CMISQL query will return the document.		* Documents are not immediately queryable after their metadata templates have been edited in Box. If you have just added/edited fields in a Box document's metadata template, there is some lag time between when Grooper can query that data. You may need to wait several hours before a CMISQL query will return the document.
	* We have encountered sporadic issues when using aliases (i.e. SELECT propertyName AS 'AliasName') in a Box CMIS Lookup query. As such, CMIS Lookups used to populate Grooper fields may be unreliable. However, please continue to report this issue to the support team at support@bisok.com. Additional reports will help the QA team diagnose this issue and help the Development team implement a solution, if possible.<section end="box_query_limitations" />		* We have encountered sporadic issues when using aliases (i.e. SELECT propertyName AS 'AliasName') in a Box CMIS Lookup query. As such, CMIS Lookups used to populate Grooper fields may be unreliable. However, please continue to report this issue to the support team at support@bisok.com. Additional reports will help the QA team diagnose this issue and help the Development team implement a solution, if possible.

			'''Best practice advice: Limit the number of files in a single folder'''
			* Thousands of objects in a single folder can cause slow preflight checks on import and export operations.
			* You can increase Box's performance by creating a nested folder strategy, limiting the number of files you place in each folder.<section end="box_query_limitations" />

	=== Upgrade issues ===		=== Upgrade issues ===

Dgreenwood: /* Box CMISQL Query limitations */

2025-09-08T21:13:07Z

Box CMISQL Query limitations

← Older revision		Revision as of 16:13, 8 September 2025
Line 650:		Line 650:
	Box has some documented limitations in its CMIS implementation in general. In most cases, Grooper is able to circumvent these issues, but not in all cases. Grooper is only able to return what Box gives us when executing a CMISQL query.		Box has some documented limitations in its CMIS implementation in general. In most cases, Grooper is able to circumvent these issues, but not in all cases. Grooper is only able to return what Box gives us when executing a CMISQL query.
	* Documents are not immediately queryable after their metadata templates have been edited in Box. If you have just added/edited fields in a Box document's metadata template, there is some lag time between when Grooper can query that data. You may need to wait several hours before a CMISQL query will return the document.		* Documents are not immediately queryable after their metadata templates have been edited in Box. If you have just added/edited fields in a Box document's metadata template, there is some lag time between when Grooper can query that data. You may need to wait several hours before a CMISQL query will return the document.
	* We have encountered sporadic issues when using aliases (i.e. SELECT propertyName AS 'AliasName') in a CMIS Lookup query. As such, CMIS Lookups used to populate Grooper fields may be unreliable. However, please continue to report this issue to the support team at support@bisok.com. Additional reports will help the QA team diagnose this issue and help the Development team implement a solution, if possible.<section end="box_query_limitations" />		* We have encountered sporadic issues when using aliases (i.e. SELECT propertyName AS 'AliasName') in a Box CMIS Lookup query. As such, CMIS Lookups used to populate Grooper fields may be unreliable. However, please continue to report this issue to the support team at support@bisok.com. Additional reports will help the QA team diagnose this issue and help the Development team implement a solution, if possible.<section end="box_query_limitations" />

	=== Upgrade issues ===		=== Upgrade issues ===

Dgreenwood: /* Box CMISQL Query limitations */

2025-09-08T21:11:06Z

Box CMISQL Query limitations

← Older revision		Revision as of 16:11, 8 September 2025
Line 634:		Line 634:
	=== Box CMISQL Query limitations ===		=== Box CMISQL Query limitations ===
	<section begin="box_query_limitations" />		<section begin="box_query_limitations" />
	Search values are required for Box CMISQL Queries. You ~~use~~ include a WHERE clause with at least one valid search condition.		Search values are required for Box CMISQL Queries. You must include a WHERE clause with at least one valid search condition.


Line 648:		Line 648:


	In ~~testing~~ Box CMISQL ~~queries, we have discovered documents~~ are not immediately queryable after their metadata templates have been edited in Box. If you have just added/edited fields in a Box document's metadata template, there is some lag time between when Grooper can query that data. You may need to wait several hours before a CMISQL query will return the document.<section end="box_query_limitations" />		Box has some documented limitations in its CMIS implementation in general. In most cases, Grooper is able to circumvent these issues, but not in all cases. Grooper is only able to return what Box gives us when executing a CMISQL query.
			* Documents are not immediately queryable after their metadata templates have been edited in Box. If you have just added/edited fields in a Box document's metadata template, there is some lag time between when Grooper can query that data. You may need to wait several hours before a CMISQL query will return the document.
			* We have encountered sporadic issues when using aliases (i.e. SELECT propertyName AS 'AliasName') in a CMIS Lookup query. As such, CMIS Lookups used to populate Grooper fields may be unreliable. However, please continue to report this issue to the support team at support@bisok.com. Additional reports will help the QA team diagnose this issue and help the Development team implement a solution, if possible.<section end="box_query_limitations" />

	=== Upgrade issues ===		=== Upgrade issues ===

Dgreenwood: /* Box CMISQL Query limitations */

2025-07-14T15:37:43Z

Box CMISQL Query limitations

← Older revision		Revision as of 10:37, 14 July 2025
Line 648:		Line 648:


	In testing Box CMISQL queries, we have discovered documents ~~who have metadata template applied to them~~ are not immediately queryable. If you have just added a metadata template ~~to a document in Box~~, ~~you~~ may need to wait several hours before a CMISQL query will return it.<section end="box_query_limitations" />		In testing Box CMISQL queries, we have discovered documents are not immediately queryable after their metadata templates have been edited in Box. If you have just added/edited fields in a Box document's metadata template, there is some lag time between when Grooper can query that data. You may need to wait several hours before a CMISQL query will return the document.<section end="box_query_limitations" />

	=== Upgrade issues ===		=== Upgrade issues ===

Dgreenwood: /* Box CMISQL Query limitations */

2025-07-14T13:45:44Z

Box CMISQL Query limitations

← Older revision		Revision as of 08:45, 14 July 2025
Line 645:		Line 645:
	The Box binding does not support does not support the <code>IN_FOLDER</code> predicate.		The Box binding does not support does not support the <code>IN_FOLDER</code> predicate.
	* You must use the <code>IN_TREE</code> predicate instead when selecting a folder location to query.		* You must use the <code>IN_TREE</code> predicate instead when selecting a folder location to query.
	* Be aware the <code>IN_TREE</code> search is recursive where <code>IN_FOLDER</code> is not. This means any subfolders will be queried as well as the targeted folder.<section end="box_query_limitations" />		* Be aware the <code>IN_TREE</code> search is recursive where <code>IN_FOLDER</code> is not. This means any subfolders will be queried as well as the targeted folder.


			In testing Box CMISQL queries, we have discovered documents who have metadata template applied to them are not immediately queryable. If you have just added a metadata template to a document in Box, you may need to wait several hours before a CMISQL query will return it.<section end="box_query_limitations" />

	=== Upgrade issues ===		=== Upgrade issues ===

Dgreenwood: /* Box CMISQL Query limitations */

2025-07-11T16:20:24Z

Box CMISQL Query limitations

← Older revision		Revision as of 11:20, 11 July 2025
Line 635:		Line 635:
	<section begin="box_query_limitations" />		<section begin="box_query_limitations" />
	Search values are required for Box CMISQL Queries. You use include a WHERE clause with at least one valid search condition.		Search values are required for Box CMISQL Queries. You use include a WHERE clause with at least one valid search condition.


	The Box API has some built in requirements to perform search queries. This is not something Grooper can get around. In the past, this has caused Grooper users a lot of confusion when configuring <code>WHERE</code> clauses in CMISQL search queries.		The Box API has some built in requirements to perform search queries. This is not something Grooper can get around. In the past, this has caused Grooper users a lot of confusion when configuring <code>WHERE</code> clauses in CMISQL search queries.
Line 640:		Line 641:
	:* Created by (cmis:createdBy)		:* Created by (cmis:createdBy)
	:* Modified by (cmis:lastModifiedBy)		:* Modified by (cmis:lastModifiedBy)


	The Box binding does not support does not support the <code>IN_FOLDER</code> predicate.		The Box binding does not support does not support the <code>IN_FOLDER</code> predicate.

Dgreenwood: /* Box CMISQL Query limitations */

2025-07-11T16:20:05Z

Box CMISQL Query limitations

← Older revision		Revision as of 11:20, 11 July 2025
Line 634:		Line 634:
	=== Box CMISQL Query limitations ===		=== Box CMISQL Query limitations ===
	<section begin="box_query_limitations" />		<section begin="box_query_limitations" />
			Search values are required for Box CMISQL Queries. You use include a WHERE clause with at least one valid search condition.

	The Box API has some built in requirements to perform search queries. This is not something Grooper can get around. In the past, this has caused Grooper users a lot of confusion when configuring <code>WHERE</code> clauses in CMISQL search queries.		The Box API has some built in requirements to perform search queries. This is not something Grooper can get around. In the past, this has caused Grooper users a lot of confusion when configuring <code>WHERE</code> clauses in CMISQL search queries.
			: To avoid confusion the following properties are not queryable at this time:
			:* Created by (cmis:createdBy)
			:* Modified by (cmis:lastModifiedBy)

			The Box binding does not support does not support the <code>IN_FOLDER</code> predicate.
			* You must use the <code>IN_TREE</code> predicate instead when selecting a folder location to query.
			* Be aware the <code>IN_TREE</code> search is recursive where <code>IN_FOLDER</code> is not. This means any subfolders will be queried as well as the targeted folder.<section end="box_query_limitations" />

	~~To avoid confusion the following properties are not queryable at this time:~~
	* Created by (cmis:createdBy)
	* Modified by (cmis:lastModifiedBy)
	~~<section end="box_query_limitations" />~~
	=== Upgrade issues ===		=== Upgrade issues ===
	There is a known issue upgrading Box '''CMIS Repositories''' from 2.9 to 2021 and beyond. The way '''''Import''''' and '''''Export Mappings''''' are configured changed radically from version 2.9 to 2021. Further, the Box binding was dramatically improved in version 2021.		There is a known issue upgrading Box '''CMIS Repositories''' from 2.9 to 2021 and beyond. The way '''''Import''''' and '''''Export Mappings''''' are configured changed radically from version 2.9 to 2021. Further, the Box binding was dramatically improved in version 2021.

	Due to this, you may experience issues with your '''''Import''''' or '''''Export Mappings''''' when upgrading to 2021 and beyond. You may need to manually reconfigure your '''''Import''''' or '''''Export Mappings''''' upon upgrading. If you are using a Box connection, please validate your mappings and test them upon upgrading to ensure they behave appropriately.		Due to this, you may experience issues with your '''''Import''''' or '''''Export Mappings''''' when upgrading to 2021 and beyond. You may need to manually reconfigure your '''''Import''''' or '''''Export Mappings''''' upon upgrading. If you are using a Box connection, please validate your mappings and test them upon upgrading to ensure they behave appropriately.

Dgreenwood at 15:07, 13 June 2025

2025-06-13T15:07:42Z

← Older revision		Revision as of 10:07, 13 June 2025
Line 10:		Line 10:
	\|		\|
	You may download the ZIP(s) below and upload it into your own Grooper environment (version 2025). The first contains one or more '''Projects''' with resources used in examples throughout this article. The second contains one or more '''Batches''' of sample documents.		You may download the ZIP(s) below and upload it into your own Grooper environment (version 2025). The first contains one or more '''Projects''' with resources used in examples throughout this article. The second contains one or more '''Batches''' of sample documents.
	* [[Media:~~2025Wiki-~~Box-Projects.zip]]		* [[Media:2025 Wiki Box Projects.zip]]
	* [[Media:~~2025Wiki-~~Box-Batches.zip]]		* [[Media:2025 Wiki Box Batches.zip]]

	Please note the Projects ZIP does not contain the configured CMIS Connection or Export Behaviors that are referenced in this article. You will need your own Box account to fully configure these resources.		Please note the Projects ZIP does not contain the configured CMIS Connection or Export Behaviors that are referenced in this article. You will need your own Box account to fully configure these resources.

Dgreenwood at 13:16, 13 June 2025

2025-06-13T13:16:32Z

← Older revision		Revision as of 08:16, 13 June 2025
Line 10:		Line 10:
	\|		\|
	You may download the ZIP(s) below and upload it into your own Grooper environment (version 2025). The first contains one or more '''Projects''' with resources used in examples throughout this article. The second contains one or more '''Batches''' of sample documents.		You may download the ZIP(s) below and upload it into your own Grooper environment (version 2025). The first contains one or more '''Projects''' with resources used in examples throughout this article. The second contains one or more '''Batches''' of sample documents.
	* [[Media:~~2025_Wiki_Box_Projects~~.zip]]		* [[Media:2025Wiki-Box-Projects.zip]]
	* [[Media:~~2025_Wiki_Box_Batches~~.zip]]		* [[Media:2025Wiki-Box-Batches.zip]]

	Please note the Projects ZIP does not contain the configured CMIS Connection or Export Behaviors that are referenced in this article. You will need your own Box account to fully configure these resources.		Please note the Projects ZIP does not contain the configured CMIS Connection or Export Behaviors that are referenced in this article. You will need your own Box account to fully configure these resources.

Dsmith: /* Configuring an Import Job */

2025-05-29T18:56:54Z

Configuring an Import Job

← Older revision		Revision as of 13:56, 29 May 2025
Line 234:		Line 234:
	# Click <code> "☰" </code> and go through the Node Type Objects within the dropdown list until you reach the Box Repository and select it.		# Click <code> "☰" </code> and go through the Node Type Objects within the dropdown list until you reach the Box Repository and select it.
	# Configure the CMIS Query by clicking <code> "..." </code> to bring up the editor window.		# Configure the CMIS Query by clicking <code> "..." </code> to bring up the editor window.
	#		# If you are processing a Batch upon importing, then configure the Batch Creation property; otherwise click Submit to submit the Import Job.
	#		# Grooper will display the Import Job in the list window, where you can monitor its status.
	#		# Once completed, you can view the imported Batch by going to the Design page and clicking ''Batches --> Test --> Imported Batches'' and selecting the newly imported Batch.
			#* Grooper will organized imported Batches by the date and time the Import Job was submitted.
			#* If you processed the Batch upon importing, it will be in the Productions Folder instead.

	== Export documents using Box ==		== Export documents using Box ==