Edit IP field on assets

This just doesn't work as a drop down. There are just too many possible ip addresses. How can we change this to a free text field?

I assume that you are referring to one of the pre-defined custom fields that you've renamed to "IP".
Double click the field label (currently "IP"), a window will open. Navigate to the 'Field Behavior' tab and un-check the check box 'Entered value must be in list'. This will allow you to type free text in this field.

Hope this helps.
Dina

They are probably referring to the IP Address field on the Details tab. The field is set to be a list but by default the value is not required to be on the list. Should be able to enter any value you like, if there are entries already on the list that are cluttering things up just remove them from the list and just leave the list blank.

The problem is actually more on the web interface, since it is a drop down, we can't enter text.

Even on the client, how can we get rid of the list all together, i just want a fill in field. Most assets have different ip addresses.

Thanks for the clarification.

There is a way to switch the type of a field in the Web interface from a drop down selection type into a textual field

In order to convert a field to accept manual text input carefully follow the instructions below:

1. Create a new empty textual file called: CmtForceTextFlds.txt and save it under folder \RangerMSP\WebInterface.

2. Decide which drop down files you want to convert into textual ones in the Web interface.

3. For each field of step #2 log into RangerMSP client right-click the field and from the menu select 'Field Settings'. A window opens - navigate to the 'Advanced' and copy the value of 'Tech. Rec ID' into your clipboard.

4. Paste the value you copied in the previous step into the newly created files (CmtForceTextFlds.txt).

5. Repeat steps #3 and #4 as need.

IMPORTANT NOTES:
* Each field ID should be stored in a new line in the text file. Do not store more than one field ID in a single line
* You should only apply the above to regular drop down fields like - City, Field1, Category, etc. - Never apply the above to special drop down lists like Ticket Status, Ticket Priority etc.

6. Save the file.

7. Restart RangerMSPWebInterface service on your server.

Done!

I hope this helps.

Thanks,
Dina

How do we do that on the client as well, for system fields - not custom ones?

Hi Luke,

The above will work for any predefined RangerMSP field that is listed in the Web interface for both employee and customers. If it's a standard drop down list of values it can be converted into a textual field.

If you're asking about the RangerMSP client application then while you cannot remove the option for a drop down with values you can set the fields properties that the value does not have to be from the list which means that it becomes a standard textual field and you will not use the drop down. For this double click the field label - the field properties window will open where you will be able to set it in a way that the entered value doesn't have to be from the list (can be applied to System field as well, not just customized ones).

Hope this helps.
Dina

Looks simple....lol

I will give it a go. Thanks.

Dina,

A small problem with your solution: While it is true that you can type any value into the field as describes (and it does not have to be on the list), if you click into such a field, the first character you type brings the list selection up, and often is not recorded. If you are not aware of this you end up losing the first digit you type, which could have a huge effect on a value (try losing the first 1 in $1251995.00!!)

Lawrence

Thanks Lawrence. However, I checked and couldn't reproduce it. When it comes to value selection list, the system recommends a value when you type (if it found one on the list) however you do not loose the first character typed if you simply keep on typing. You provided an example with amounts so maybe you are referring to something else, not fields with drop downs.

Hope this makes sense.
Dina

Commit, that solution works like a charm! I didn't notice the first digit issues like lbrickpe did. That does happen when using the client thought.