|
|
|
|
|
by bigmattystyles
859 days ago
|
|
The problem is when your instance has too many masters - all fields are global, then their visibility is controlled at the project level. In a big company with one instance, holy sh!t. There are so many duplicated fields, unused fields. When you go to the bulk change option, it shows you all of these and it goes for days.
It works well if you keep it under control, but word to the wise to any company. Create a governance board that's not afraid to tell a VP to fuck off with their requests for yet another ill-conceived field.
That's from the user / web viewpoint.
Don't get me started on their API. v2, v3 changes - the stuff you can't filter out that bloat responses, etc....
But otherwise, if well controlled, it is good. Or at least one of the least bad systems. |
|