Skip to main content
Solved

Increase the maximum number of characters allowed in Commvault VSA subclient description error


Forum|alt.badge.img+10

Would you ask the Commvault if they can increase the number of characters allowed in Commvault VSA subclient description field to 10,000

 

Best answer by chrisknows

Graham Swift wrote:
gary mcneely wrote:

Audit tab option  as in pull a report ?

pseudo-tags, instead of actual tags , can you please add a screenshot of what that looks like

Hello @gary mcneely ,

Not the report. If you look at the properties of client you will see there is an audit tab.

You can add information in there and set a severity etc. But it is a write once read type of setting so give you an historical record of what is changing on the client. Very useful way to avoiding using the description field as a way to track changes. These are limited to 256 characters though but usually enough to detail what has changed.

If you are looking to automate it, using the workflow engine you can use the execute command:

and then add some XML like so:

<App_SetEntityAuditReq> 
    <entity _type_="3" clientName="xpath:{/workflow/inputs/client}"/> 
    <entityAuditList notes="add your information you want to record here" severity="1">
        <user userId="xpath:{/workflow/system/executor/userId}" userName="xpath:{/workflow/system/executor/userName}"/> 
    </entityAuditList>
</App_SetEntityAuditReq>

That audit note thing is genuinely useful. 

Thanks.

View original
Did this answer your question?

12 replies

chrisknows
Byte
Forum|alt.badge.img+10
  • Byte
  • 82 replies
  • December 7, 2022

That seem’s unreasonable… why would you need 10,000 characters for a description?

That's more like a treatise.

 

There are short stories that use less than 10,000 characters.


Forum|alt.badge.img+10
  • Author
  • Byte
  • 38 replies
  • December 7, 2022

What about 6000 characters ?

 


Graham Swift
Vaulter
Forum|alt.badge.img+11

@gary mcneely what are you using the description field for?

If as I see many customers doing, notes on changes being made. We have an Audit tab option which can be used to track this in a much better way. ie the details can’t be doctorred etc…

Would that work for you?


Forum|alt.badge.img+3

I have seen people use descriptions as pseudo-tags, instead of actual tags, which to be fair is a relatively new feature


Forum|alt.badge.img+10
  • Author
  • Byte
  • 38 replies
  • December 12, 2022

Audit tab option  as in pull a report ?

pseudo-tags, instead of actual tags , can you please add a screenshot of what that looks like


Onno van den Berg
Commvault Certified Expert
Forum|alt.badge.img+19
  • Commvault Certified Expert
  • 1200 replies
  • December 12, 2022

@gary mcneely  Curious to hear the use-case why you want to be able to log so much information in the description field. As for the tag functionality see → https://documentation.commvault.com/2022e/essential/139220_creating_tag_for_entity.html


christopherlecky
Byte
Forum|alt.badge.img+16
gary mcneely wrote:

Audit tab option  as in pull a report ?

pseudo-tags, instead of actual tags , can you please add a screenshot of what that looks like

I don’t have screenshots but people have posted it where in the description field they would do something like so. 

CompanyName = MyCompany
TenantName  = Tenant1
BillingID   = 4001

Essentially using the description as a way to add tags to different parts of the hierarchy. 

This of course then requires large description fields and some method of parsing the description text.

Since tags are now supported this shouldn't be necessary anymore


Graham Swift
Vaulter
Forum|alt.badge.img+11
gary mcneely wrote:

Audit tab option  as in pull a report ?

pseudo-tags, instead of actual tags , can you please add a screenshot of what that looks like

Hello @gary mcneely ,

Not the report. If you look at the properties of client you will see there is an audit tab.

You can add information in there and set a severity etc. But it is a write once read type of setting so give you an historical record of what is changing on the client. Very useful way to avoiding using the description field as a way to track changes. These are limited to 256 characters though but usually enough to detail what has changed.

If you are looking to automate it, using the workflow engine you can use the execute command:

and then add some XML like so:

<App_SetEntityAuditReq> 
    <entity _type_="3" clientName="xpath:{/workflow/inputs/client}"/> 
    <entityAuditList notes="add your information you want to record here" severity="1">
        <user userId="xpath:{/workflow/system/executor/userId}" userName="xpath:{/workflow/system/executor/userName}"/> 
    </entityAuditList>
</App_SetEntityAuditReq>


Graham Swift
Vaulter
Forum|alt.badge.img+11

As for tags, these are managed in Command Center.

And if you want to automate these then use the API:

PUT https://{{serverUrl}}/Tags

{
  "entityTag": [
    {
      "entityId": 279,
      "entityType": 3,
      "tag": [
        {
          "name": "name1",
          "value": "value1"
        },
        {
          "name": "name2",
          "value": "value2"
        }
      ]
    }
  ]
}

Tags a useful to then make use of to add to Client groups, plans, include in reports etc...


chrisknows
Byte
Forum|alt.badge.img+10
  • Byte
  • 82 replies
  • Answer
  • December 19, 2022
Graham Swift wrote:
gary mcneely wrote:

Audit tab option  as in pull a report ?

pseudo-tags, instead of actual tags , can you please add a screenshot of what that looks like

Hello @gary mcneely ,

Not the report. If you look at the properties of client you will see there is an audit tab.

You can add information in there and set a severity etc. But it is a write once read type of setting so give you an historical record of what is changing on the client. Very useful way to avoiding using the description field as a way to track changes. These are limited to 256 characters though but usually enough to detail what has changed.

If you are looking to automate it, using the workflow engine you can use the execute command:

and then add some XML like so:

<App_SetEntityAuditReq> 
    <entity _type_="3" clientName="xpath:{/workflow/inputs/client}"/> 
    <entityAuditList notes="add your information you want to record here" severity="1">
        <user userId="xpath:{/workflow/system/executor/userId}" userName="xpath:{/workflow/system/executor/userName}"/> 
    </entityAuditList>
</App_SetEntityAuditReq>

That audit note thing is genuinely useful. 

Thanks.


Forum|alt.badge.img+10
  • Author
  • Byte
  • 38 replies
  • December 19, 2022

thank you

 


Forum|alt.badge.img+4
chrisknows wrote:
Graham Swift wrote:
gary mcneely wrote:

Audit tab option  as in pull a report ?

pseudo-tags, instead of actual tags , can you please add a screenshot of what that looks like

Hello @gary mcneely ,

Not the report. If you look at the properties of client you will see there is an audit tab.

You can add information in there and set a severity etc. But it is a write once read type of setting so give you an historical record of what is changing on the client. Very useful way to avoiding using the description field as a way to track changes. These are limited to 256 characters though but usually enough to detail what has changed.

If you are looking to automate it, using the workflow engine you can use the execute command:

and then add some XML like so:

<App_SetEntityAuditReq> 
    <entity _type_="3" clientName="xpath:{/workflow/inputs/client}"/> 
    <entityAuditList notes="add your information you want to record here" severity="1">
        <user userId="xpath:{/workflow/system/executor/userId}" userName="xpath:{/workflow/system/executor/userName}"/> 
    </entityAuditList>
</App_SetEntityAuditReq>

That audit note thing is genuinely useful. 

Thanks.

 

Hey! How can this be done using the APIs?


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings