This has been a problem for as long as I've been dealing with Sage CRM (15 years). There is still no decent solution to this. Of all the potential solutions I've found, there is always a way to mess it up. You can get creative with using RemoveLookup but that only works when loading the screen and changing to edit mode. With the clientside scripting you might be able to do it more easily now. You will first need a custom content script on the page which contains a function to hold the states. The in the onchange you call that function based on the selected value. The function removes everything when the selected value is blank so you can't save anything in finish options without a value in finish type. When you choose a value in type, it reloads the correct values in options. You will need to make sure the correct values are set when doing this, so that when you save, the right form values are there in the dropdowns. It's a right pain to implement. It's a very commonly asked for feature. No decent solution exists on the forum that I've found. It's a common thing in many other CRM systems.

This has been a problem for as long as I've been dealing with Sage CRM (15 years). There is still no decent solution to this. Of all the potential solutions I've found, there is always a way to mess it up. You can get creative with using RemoveLookup but that only works when loading the screen and changing to edit mode. With the clientside scripting you might be able to do it more easily now. You will first need a custom content script on the page which contains a function to hold the states. The in the onchange you call that function based on the selected value. The function removes everything when the selected value is blank so you can't save anything in finish options without a value in finish type. When you choose a value in type, it reloads the correct values in options. You will need to make sure the correct values are set when doing this, so that when you save, the right form values are there in the dropdowns. It's a right pain to implement. It's a very commonly asked for feature. No decent solution exists on the forum that I've found. It's a common thing in many other CRM systems.

Thank you for the response Vega, don't suppose you could through together a brief example of this function, you are referencing towards.