Asset additional fields pick list values workaround.
There is an issue is that numerical values are shown in ascending order under the Asset picklist additional field.
If a user complains about this specific issue, it is because Pick List values are stored as string in the database, so the fields are being rendered in the form based on string-based sorting.
So instead of using 1,2,3,4,5,6,7,8,9,10,
we can suggest this 01,02,03,04,05,06,07,08,09,10,
New to ADSelfService Plus?
Related Articles
Additional field values
This report helps to find the picklist values in the additional fields. First you need to find the name of the table and the column holding the data, by executing the following SDP query report: SELECT Tablename, Columnname FROM ColumnAliases WHERE ...API -Listing requests based on Additional Field Values
This can be met through V3 API. Go to Admin > Incident Additional Fields and make a note of the "API Field Name" as highlighted below: Please follow the below mentioned to pull the requests based on the additional field values: 1. Use the Input as ...Script to Populate User Additional Field under Incident Template using FAFR
The script load the Requester Name under Incident Additional field ( As a pick list), by choosing the requester name under additional field the script populates the user additional field value. * Kindly create two additional fields under Admin -> ...Query to retrieve Account details along with additional attributes, postal address and additional fields data
TESTED IN BUILDS: 14700 (Postgres) QUERY 1 - Without Account Additional Fields: select ad.ORG_NAME As "Account", org.description AS "DESCRIPTION", ad.LOGIN_WEBURI AS "LOGIN WEB URL", ad.LOGIN_URI AS "LOGIN URI", ad.SUPPORT_EMAIL AS "SUPPORT EMAIL", ...How to import user additional fields using LDAP
In order to import additional fields or map any other fields in AD to the system fields, a row needs to be updated with the appropriate values You can follow the below steps 1. Take a trimmed backup of the database. 2. Connect to the Database 4. Run ...