<style>p { margin: 0; }span.fr-emoticon.fr-emoticon-img { background-repeat: no-repeat !important; font-size: inherit; height: 1em; width: 1em; min-height: 20px; min-width: 20px; display: inline-block; margin: -0.1em 0.1em 0.1em; line-height: 1; vertical-align: middle; } span.fr-emoticon { font-weight: normal; font-family: "Apple Color Emoji", "Segoe UI Emoji", "NotoColorEmoji", "Segoe UI Symbol", "Android Emoji", "EmojiSymbols"; display: inline; line-height: 0; } blockquote { border-left: solid 2px #5e35b1; color: #5e35b1; margin-left:0; padding-left:5px;}blockquote blockquote{ border-color: #00bcd4; color: #00bcd4;}blockquote blockquote blockquote{ border-color: #43a047; color: #43a047;} table.grid{ border-collapse: collapse;} table.grid td, table.grid th { border: 1px solid #ddd;} .fr-fic.fr-dib{ display: block; margin: 5px auto;}.fr-fic.fr-dib.fr-fir{ text-align: right; margin: 5px 0 5px auto;}.fr-fic.fr-dib.fr-fil{ text-align: left; margin: 5px auto 5px 0;}.fr-fic.fr-dii{ float: none; margin: 5px auto;}.fr-fic.fr-dii.fr-fil{ float: left; margin: 5px auto;}.fr-fic.fr-dii.fr-fir{ float: right; margin: 5px auto;}img.fr-dib.fr-fir { margin-right: 0; text-align: right;}img.fr-dib.fr-fil { margin-left: 0; text-align: left;}img.fr-dib { margin: 5px auto; display: block; float: none;}img.fr-bordered { box-sizing: content-box; border: solid 5px #CCC;}img.fr-shadow { box-shadow: 10px 10px 5px 0px #cccccc;}img.fr-rounded { border-radius: 10px; -moz-border-radius: 10px; -webkit-border-radius: 10px; -moz-background-clip: padding; -webkit-background-clip: padding-box; background-clip: padding-box;}</style><p><strong>In this guide we will cover:</strong></p><p><strong>- Enabling the New Value Storage Method</strong></p><p><strong>- Selecting a Storage Method</strong></p><p><strong>- Differences Between the Two</strong></p><p><br></p><p><br></p><p><strong><span style="font-size: 14pt;">Enabling the New Value Storage Method</span></strong></p><p>The new value storage method can be enabled within Configuration > Advanced Settings > Performance section, by enabling the following checkbox.</p><p><br></p><p><em><strong>Note: This method will only apply to custom fields made after enabling the below.</strong></em></p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjY0MmI4N2IyLWY0MjctNDFjYi1iNGI1LTIyM2ZkOTZjMDEyZiJ9.MCq22Q-l0SzqJhtdE_TUxXkg-dA6QQhxjIrTrdRJfgU" class="fr-fic fr-fil fr-dib" width="699" height="61"></p><p><strong><span style="font-size: 10pt;">Fig 1. Enabling the new storage method.</span></strong></p><p><br></p><p><strong><span style="font-size: 14pt;">Selecting a Storage Method</span></strong></p><p>Upon enabling the above, a field named "Value storage location" will show when creating a new custom field. This will show two options: storing in a row versus a table.</p><p><br></p><ul><li>Storing in a row will store the field in the FieldData table, and is recommended for small numbers of ticket types.</li><li>Storing in a column will store the field in a new column in the table the field belongs to, and store the value in the same row as the entity. This is recommended for fields within a larger number of ticket types, or commonly used when listing tickets or within global searches.</li></ul><p><br></p><p>If you have a larger database, storing in a row is recommended mostly as this can reduce the size of the table it is contained in, and therefore increasing performance.</p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImIwYjM4NWY5LWNkNjYtNDBmMy04NzMwLTE3OWY2NWM1MzUxYyJ9.Joq_ggdg8wVCFqdVB89gQ5pudLJmQSRprJqUyWUlTqw" class="fr-fic fr-fil fr-dib" width="1218" style="width: 1220px; height: 472.363px;" height="472"></p><p><strong><span style="font-size: 10pt;">Fig 2. Selecting a storage method.</span></strong></p><p><br></p><p><strong><span style="font-size: 14pt;">Differences Between the Two</span></strong></p><p>If storing in a column, the data will show in its assigned table for the entity as normal, i.e. "faults".</p><p><br></p><p>If storing in a row, the data will show in the "FieldData" table instead of its assigned table for the entity. The "fdFieldId" will pull the ID number of the custom field, and the "fdValueString"/"fdDisplay" the value(s) within the field.</p><p><br></p><p>Row is generally recommended due to the increased performance, however column is suggested for fields that are present in a larger number of ticket types or often globally searched.</p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjE3MjUzZjZlLThiOGUtNDZkNy1hYTViLThjYzU5ZWVhMzE3MSJ9.afK30SwYI3AKj6Ozr1DIRSJFDluScfuRdxmHYzU8Qbw" class="fr-fic fr-fil fr-dib" width="807" height="668"></p><p><strong><span style="font-size: 10pt;">Fig 3. FieldData table.</span></strong></p><p><br></p>
