Also, Aware will get confused if you rename a field in a table, and before publishing add another field of the same name in the same table.
(example: In the Cust table, you have a field "sales". You realize you're going to use that as "sales_ytd" so you simply rename the field. No issues here.
But you still want a sales field for another reason, so now you make new field "sales".
I'm pretty sure this will confuse aware to some extent. Its gotten better over the years (and quite frankly, its amazing the job Vlad has done to begin with for Aware to keep all the changes straight and apply them for us behind the scenes - amazeballs!). Anyway, the way to make this work would be to save/test/publish with only the rename. Then make new version and add the new field. Will not fail now.)
This is the SAFE foolproof way where Aware cannot get confused.
All it takes is one of these episodes (like you are now in) to delay you and cause stress, to then make you want to do it safely in the future.
If you did LOTS of changes and aware gets confused, instead of a single message like you're getting now, you can get SEVERAL - and then its lots of work to get back functioning.
So, when messing with relationships, adding/deleting, best to do baby steps and save & publish often.
Thats my $.02 - your mileage may vary
