Number of Objects in client does match after load of transport case
Article ID: 400740
Updated On:
Products
Issue/Introduction
When unloading a transport case for a full client and loading the transport case into a new client, going to the Administration Perspective --> Client Management --> Clients --> Number of objects does not match, the source client where the transport is unloaded, shows a higher number than the target client where they are loaded into. How can we find which ones were not loaded?
For example:
source client shows 202 in the below Number of objects:
target client shows a lower number, in this case 196:
Cause
This is as designed, caused by the number of empty folders in the source client
Resolution
This behavior is as designed. The difference between the clients, assuming the target client only had a user used to load the transport case, is going to be caused by empty folders in the source client. Empty folders are not unloaded into the transport case.
You can find this by running a SQL statement like:
select count(*), oh_otype from oh where oh_client = [source or destination client number] and oh_deleteflag = 0 group by oh_otype order by count(*)
Running this against each client might show something like this for the source (left) client and target (right) client
Notice that the only difference in these is the FOLD type or folder - in further review of these objects by looking at oh_otype in the oh table, you'll notice that only empty folders (or folders containing only empty folders) will be missing in the target client.
Additional Information
Do remember that this can be for on-premise or for SaaS environments.
Feedback
