First, thank you for adding "ClosedDate" to the API calls. It is imminently helpful.
Here's a suggestion that would help us, and perhaps others...
We pull our data into a matter management system using the API... sometimes we will have an error in the import that is caused by our own error in data entry into B4T. For example, in creating a client, a user entered erroneously entered a phone number (or put an "n/a" in the email field. B4T will accept such an entry but our project management suite will not. This caused an import error. It was easy to find the offending clients and make the necessary corrections... but if B4T steered data entry in the right direction, that may be helpful.
So the suggestion is this: In email fields, require that the entry have an @ in it, i.e. require the user to enter an email address rather than a number or "N/A" or seomthing else
Please sign in to leave a comment.