Absent Member.. MichaelOne Absent Member..
Absent Member..
376 views

Modifing Request and Request Header types

Jump to solution

When I want to add a field to an existing request type, I'll get a message box "(KCRT-40074) stating this request type is already being used in # request types.   If you want to make changes ...... Instead, it is strongly recommended that you copy this request make changes to the copy ...... use the new request type after making changes".

 

How does this work? Each time a modification is needed a new request type has to be created? What would be the naming convention? Is there a manual on error messages?  

 

thanks

 

michael  

0 Likes
1 Solution

Accepted Solutions
Jason Nichols K Absent Member.
Absent Member.

Re: Modifing Request and Request Header types

Jump to solution

Michael,

 

I'm not aware of any manuals on the error messages.  This particular message appears anytime to try to make any changes to a Request Type (or Header Type) that has already been used in a Request.  If you make a copy of the Request Type, any existing Requests that are using the old Request Type will not see the updates.  Generally, I've not had any problems adding fields to existing Requests, or even disabling fields that are no longer necessary.  You run into issues when you trying moving the parameter that a field is using or deleting a field and then re-using the parameter that the deleted field was using.  It's a matter of data integrity.  Deleting a field from a Request Type will not delete the data in any existing Requests that have already been created.  Likewise, moving the parameter that a field is stored in will not move the data in the database.

 

Basically, this is just a warning message to make you realize that any changes you make could have implications to existing Requests that have been created using the Request Type you now wish to change. 

 

Jason

0 Likes
2 Replies
Jason Nichols K Absent Member.
Absent Member.

Re: Modifing Request and Request Header types

Jump to solution

Michael,

 

I'm not aware of any manuals on the error messages.  This particular message appears anytime to try to make any changes to a Request Type (or Header Type) that has already been used in a Request.  If you make a copy of the Request Type, any existing Requests that are using the old Request Type will not see the updates.  Generally, I've not had any problems adding fields to existing Requests, or even disabling fields that are no longer necessary.  You run into issues when you trying moving the parameter that a field is using or deleting a field and then re-using the parameter that the deleted field was using.  It's a matter of data integrity.  Deleting a field from a Request Type will not delete the data in any existing Requests that have already been created.  Likewise, moving the parameter that a field is stored in will not move the data in the database.

 

Basically, this is just a warning message to make you realize that any changes you make could have implications to existing Requests that have been created using the Request Type you now wish to change. 

 

Jason

0 Likes
Absent Member.. MichaelOne Absent Member..
Absent Member..

Re: Modifing Request and Request Header types

Jump to solution

Jason,

 

I appreciate you clarifying the error message as a warning. Whenever I see that message it sounds so definite my data will be corrupted.

 

Thanks again  

 

Michael

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.