Kevin,
We understand what you are asking about, which involves form and field entry comparison and manipulation, and I did provide a basic abstract of how to accomplish your specifics. I had indicated in a previous post:
On the surface, based purely on the requirements given, you would be looking at custom table development plus possible spel codes and triggers to control the table contents, which is most likely beyond the scope of support, especially spel code requirements. However, if we could get a use case that explains from a practical standpoint how you would use all this in Service Desk, we may be able to assist or guide towards another approach to attain your requirements.
While we can try and offer you possible direct solutions to accomplish the specifics of what you are asking about, it still does not explain what you plan to do with this functionality. We are simply asking you what your use case is at a high level. What does this table structure represent within a given service desk environment? How would you invoke the functionality and under what conditions?
We also realise the potential that the specifics of how the functionality in question is to be leveraged in your scenario is something you may prefer not to discuss here, or if you feel reluctant to do so under concern that we could potentially offer an existing solution that is already present within Service Desk that does not fit your needs. However, consider that we have been going back and forth in this posting for a week now, and I feel we can agree that we have not yet come to a suitable finding on your initial query. Providing us with the aforementioned use case would most likely help us to determine a reasonable solution to your concerns.