Nathan Phillips (CW) 11/18/2013 7:25:36 AM
For me, this creates an additional load that I now have to think about and maintain for every single table, every single time I build anything. I build a lot of tables, and the more configuration I can eliminate from each one, the faster I can build something, and the less risk of making a mistake. I make it a rule to never use the Default View because of this - then there's one less thing for me to configure on each column, which can make a significant difference if I'm adding a lot of columns. If I could simply disable Add Similar in one place, then I wouldn't need to think about it on every column.
There's also the risk that a client adds a new column to a table, and DOESN'T disable add similar. Now it's no longer working the way I configured it. Again, if I can disable the button centrally, that eliminates the risk of this happening and enables me, as a developer, to control the button now and know that it will stay that way in the future.
From a user experience perspective, my preference is to make the interface as simple as possible. There are 2 things the button affects.
One, it creates a second route for adding records. I'd really like to say to users - to add a record, you go here and use this button. And that's The Only Way to add a record. That makes it simple and clear.
Second, I will sometimes end up with a lot of custom buttons on a table. They all show up at the top of the record, along with the Delete and Add Similar and Back buttons. It can get crowded up there. The more buttons I can eliminate from that list of buttons, the simpler I can make it, and therefore the friendlier it becomes for users. I often disable deleting to eliminate that Delete button. Pulling the Add Similar button off that list would also help.
Whew. Guess I had a few reasons.