Again, I am not convinced that this was even tested before release. This defeats the purpose of naming/reusing a datasource if you have to re-alias all fields everytime you use it. As a result, the text file source has become quite useless unless you are using a csv.įield Alias for Named database connections don't store with the named connection which makes it pointless as you will need to re-alias these things every time you change datasource. After upgrading from 10.4, all tables from our XML payloads now crash bartender when you try to do ANYTHING with them (Great coding guys). SOme of the new 'features' have absolutely destroyed Database/setup connections. This is what happens when a company cuts back on 'costs' by elimiating quality assurance and customer support. Have a lot of difficulty getting answers from the tech team. Very little insight into customer service. Was this product actually run by QA before release? I suspect there was nothing but plug and play sceanrios tested. Bartender then restarts and attempts to recover the bad information (which will in turn crash bartender.) (They will still work so long as you don't touch them).
#Bartender 10.1 pricing update
The new 2016 version crashes anytime I attempt to update a database connection from one of our old XML source that worked seamlessly in 10.4. Cons: Very disappointed in the new 2016 version.
0 kommentar(er)
