Question
We reviewed the upload process and observed that created date was not retained but all other attributes (modified date, modified by and created by) were all correctly set. What could cause this?
Answer
In some cases customer try to set a created date that is more recent than the modified date. This is not allowed by SharePoint. As a result, the created date will be set to the current date.
Question
1.Is there a limit to the number of items you can be listed under a File Share Connection?
2.Is there a limit to the number of rows and columns that you can have in the File Share Edition?
3.Is there an expected amount of memory usage?
Answer
1.This partly depends on the machine that is running the Content Matrix Console. Depending on the machine it is recommended to only go as high as 5000 items under a File Share connection.
2.This is similar to the number of items. Since it is recommended to only go as high as 5000 items under a File Share connection, and each item is the same as one row in the Items View tab, we recommend to only go up to 5000 rows under a specific File Share connection. While there is no limit to this for columns, since these are only related to rows in that it is information for items, it would still be a good general rule to not exceed 5000 columns, but going over this should not be an issue.
3.Content Matrix Console uses an in memory Database (DB) for it's project files, so the amount of memory used can get quite large depending on the number or rows and columns that are included under the File Share connection. To help reduce the in-memory footprint any long strings are stored in the DB, and not in the memory. Since each user's migration scenario is different, we can't accurately give an expected amount of memory usage.
Question
Why am I getting an error when I try to connect to SharePoint 2019 or SharePoint Server Subscription Edition in a FIPS-enabled environment?
Answer
Content Matrix uses some assemblies for FIPS compliance that are not supported for certain SharePoint 2019 and SharePoint Server Subscription Edition connections.
For a remote object model (MEWS) connection (displays for the top node) for SharePoint 2019:
Client found response content type of 'text/html; charset=utf-8', but expected 'text/xml'. The request failed with the error message: -- <!DOCTYPE html> <html>
For a local object model (OM) connection (displays at the item level for SharePoint 2019 and SharePoint Server Subscription Edition):
The type initializer for 'Microsoft.SharePoint.ApplicationRuntime.SPRequestModule' threw an exception
In addition, errors will display in Browser View and Items View.
For SharePoint Server Subscription Edition, you can connect using a remote object model (MEWS) connection.
Question
Is it possible to change the configuration for multiple job files at one time in the Job List section of Content Matrix?
Answer
Yes, this is possible. Most users will only need to change the configuration of a single job in the Job List section, but it is possible to change the configuration for multiple jobs at one time.
In order to modify the configuration for multiple job files at one, select all of the jobs in the Job List section. Once all of the desired jobs are selected there are two methods that can be used to access the configuration dialog. The first is to click the Change Configuration button at the top of the Job List, and the second method is to open the context (right-click) menu, and select the Change configuration for selected jobs option.
The behavior for changing the configuration of multiple files at once changes slightly depending on the version of Content Matrix Console that is being used.
Behavior in Versions 6.1.00 and Later
When changing the configuration for multiple files that use the same type of action at once, only settings that are changed during the re-configuration will be pushed into all of the selected jobs. This means that even if all of the jobs contain different settings, they will all still contain these different settings after the configurations have been modified. Only the settings that were re-configured will be changed (to whatever setting they were changed to).
Let's look at the example of three "Paste Site" jobs that are previously configured, and each has a different Rename action applied to it as well as a few various other differences in selected options. When the Change Configuration is applied to all three at once, only the settings that were reconfigured will be affected. So if the web part options were changed, then those options will be applied to all three jobs, but each will still retain their original Rename setting, and any other settings that were configured even if there are differences.
Behavior in Versions 6.0.0201 and Earlier
When changing the configuration for multiple files that use the same type of action at once, all of the selected files will have the options for the first job in the Job List section pushed into them, regardless of any other setting the previously used. Basically, all of the jobs after the first select job in the Job List will be modified to use all of the settings from the Change Configuration dialog.
Let's look at the example of three "Paste Site" jobs that are previously configured, and each has a different Rename action applied to it as well as a few various other differences in selected options. When the Change Configuration is applied to all three at once, all of the configuration options that are set for the first of the selected jobs in the Job List will be pushed to the two remaining jobs. These two remaining jobs would then use all of the exact same configuration options as the first job, including the values for the rename options. Any of the previous settings for the two remaining jobs would be lost (because they are replaced with the first jobs configuration options).
