Your answer is something that we already now (I have already stated that in my post) . And it is very astonishing that such functionality which was oob in the Classic UI is not present in the Freedom UI.
Please give us a code example of implementing such functionality in freedom UI.
We don't have a ready example of such implementation.
However, we have already registered the idea for our R&D team to implement this functionality in further releases. I will assign your case to this project to increase its priority.
You need to create other lookups, remove and replace the current postal code text field, so that you can add postal code to the list of cities to do the links. It is indeed weird that this is a seperate text field as an OOTB feature.
Also, accounts is in Freedom UI, with customer 360, but not account adresses , how weird is that ??
This cannot be achieved in the current application version since there is no direct link to call on creating a new record (we can only pass the URL to the window.open). A new record is created via the addRecord method that in the final steps call the openCardInChain method that passes the operation: ConfigurationEnums.CardStateV2.ADD. This cannot be done with opening the new window. But I will create a suggestion for our R&D team to add this funcitonality in one of the future releases. Thank you for helping us in making the app better!
This cannot be achieved in the current application version since there is no direct link to call on creating a new record (we can only pass the URL to the window.open). A new record is created via the addRecord method that in the final steps call the openCardInChain method that passes the operation: ConfigurationEnums.CardStateV2.ADD. This cannot be done with opening the new window. But I will create a suggestion for our R&D team to add this funcitonality in one of the future releases. Thank you for helping us in making the app better!
This suggestion I registered is in the "Accepted" status so we expect this feature to be added in the app. Once it's developed and implemented we will notify about it in the Release notes of the version.
A bit of background: I need to make a business rule to filter the postcodes based on the city that is selected. The City lookup in the base package does not have postcode in the schema and therefore I can not get this done.
This lookup is in an instance which is live. I do not want to create a new City lookup and put it everywhere across the instance.
Can someone please guide me on how to edit the City Lookup that is present in the base package in a way that I can package it and install it on the live instance without affecting the values that are already in that field?
You can replace this lookup (http://prntscr.com/np7od8) and add new column to the object. Thus all functionality and data of the lookup is saved and you can add a column needed.
I created the object using "Replacing objects" and published the object. I also did the database update. I can see the lookup in the lookup section. I tried to create a new lookup, and I still only see the City lookup in the Base package. I also checked the original lookup and it still does not show the Postcode.
I am attaching the image of the object I created. Please let me know if I am making a mistake somewhere.
There is no need to create new lookup, this column will be added to existing lookup. I just tried to do the same on my instance and column was added: http://prntscr.com/np9bp3
