Project and Portfolio Management Practitioners Forum
cancel
Showing results for 
Search instead for 
Did you mean: 

Request Header - Considerations

Highlighted
Jamie Pick
Regular Collector

Request Header - Considerations

We're actively working on a project that involves several field changes and workflow changes to some of our request types. As a part of this, we've had discussions around moving fields from the header to the detail or vise-versa. We're cautious in doing this, as the header seems like a "special" area (the config guide mentions "indexes for querying").

Does anyone have any guidelines to follow regarding the considerations involved in moving fields from a header to a detail or vise-versa? How about adding custom fields to the header - any performance considerations?

Thanks,

Jamie
3 REPLIES
Sachin M
Regular Collector

Re: Request Header - Considerations

Hi Jamie,

It will not make much of a difference. In header you can have max of 50 fields and it is best practice to have all your custom fields in Details section. In details section you have six batches and each batch can have 50 fields (at max).

Hope this will help you.

Regards
Sachin
Jamie Pick
Regular Collector

Re: Request Header - Considerations

Thanks for the reply.

One of the specific things discussed was table indexing... it seems to me that Field Groups need to be a consideration, but a custom field added to the Header does not necessarily add the new column to an index, right?

Thanks,

Jamie
Mahen M
Honored Contributor

Re: Request Header - Considerations

Hi Jamie,
As Sachin told you can keep all the custom fields in Detail, The sole disadvantage is that the header has only 50 Custom fields.

The Field group items does not occupy the 50 fields in Header.

You can add any number of batches in Details, But HP advices us to use only 300 fields max.

We have done the changes by update Query, we copy values from Header and paste it in the corresponding detail table.

Checkup the attached SQL Work for you.

Regards,
Mahendran M
//Add this to "OnDomLoad" event