Customer Contract Module: It would be very helpful if we could add the standard field is_renewed as a field to the search screen for Customer Contracts. Is there a way to accomplish this?
Thanks in advance.
Solved
Adding a standard field to QBE screen
Best answer by Phil Seifert
I don’t think a computed lookup will work as that requires at least opening the record before it is potentially saved to the database.
Perhaps you can look at creating a single text column, call it Renewed. This will create a column in your cconth table; cconth.cst_renewed. This column would be available to the search.
However, it does not have any data yet… so you probably would need to run a script to copy the value from the cconth.is_renewed to the cconth.cst_renewed column. This will set up the initial data. To avoid having to run this script periodically (which you could do with a periodic process flow to look for mismatches each night during off hours as I don’t think you would renew a contract more than once in a day normally) you could also setup a process flow as save event driven which would execute the update if there is a change to the value.
I honestly would prefer a code change with a custom service request but believe the above would also work though not very elegant as it is creating more data as well as using resources each time there is a save action on a customer contract to check if it was updated or not.
+23Hi Nick,
This is a code change request if you mean to search and retrieve based on cconth.is_renewed. There is not a way to make this field available in the search without modifying the DAL, adding to the criteria selection and scroller results.
If it were a customizer field that was saved as a value with the record, these fields are added to the search automatically but not the standard fields unfortunately.
Thanks for the info Phil. We are trying to determine the best way to create a new custom field that would essentially mirror the standard field and then can be used as a search criteria. Can you advise on the best way to set this up?
+23I don’t think a computed lookup will work as that requires at least opening the record before it is potentially saved to the database.
Perhaps you can look at creating a single text column, call it Renewed. This will create a column in your cconth table; cconth.cst_renewed. This column would be available to the search.
However, it does not have any data yet… so you probably would need to run a script to copy the value from the cconth.is_renewed to the cconth.cst_renewed column. This will set up the initial data. To avoid having to run this script periodically (which you could do with a periodic process flow to look for mismatches each night during off hours as I don’t think you would renew a contract more than once in a day normally) you could also setup a process flow as save event driven which would execute the update if there is a change to the value.
I honestly would prefer a code change with a custom service request but believe the above would also work though not very elegant as it is creating more data as well as using resources each time there is a save action on a customer contract to check if it was updated or not.
Appreciate it Phil, we have similar concerns but we will give it a try and see how well it works.
+5Hi Nick
I quickly made this document for you and I tested it in my French configuration. You can adapt it to your language in SA. You can adapt it according to your needs. Hoping it suits you.
Regards
Michel
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.