AltSearchField in NAV2016

The property AltSearchField is removed in NAV2016 but importing an object from NAV2015/2013 which had that property set will still keep the property value even though it’s not visible in the development environment.

This might not be an issue until you try to rename the field that is set as AltSearchField. Then you’ll end up with an error like “You cannot enter ‘YourSearchName’ in FieldNo.”. The only way to solve this is to export the object to a txt file and manually remove the property.

Tags:

5 Responses to “AltSearchField in NAV2016”

  1. Natalie 2016-03-07 at 15:13 #

    Seems this has been corrected in Cumulative Update 5 for NAV 2016 (https://mbs2.microsoft.com/Knowledgebase/KBDisplay.aspx?scid=kb;EN-US;3145855)

    • Lars Westman 2016-03-07 at 15:16 #

      Good news! I was running on CU4

      • Natalie 2016-03-08 at 09:04 #

        Hum, I just read from another user that the property is still included when you export as text. I cannot test it myself – can YOU confirm it?

        • Lars Westman 2016-03-08 at 09:48 #

          It’s kind of fixed in CU5… Now you can rename the field without getting an error, but if you export the table to a text file the AltSearchField property will still be there with the OLD fieldname….

          You can import the text file again with the AltSearchField property and the wrong fieldname so it doesn’t cause any errors. But it isn’t pretty. Kind of fixed half way.

          • Natalie 2016-03-08 at 14:38 #

            Thanks for the information!

Leave a Reply