Field no longer used counting towards look up quota
Hello! I am having an issue with the lookup field limits.
My vertical app is published, but as I improve and make changes I am running into issues. Specifically with the lookup field limits.
SCENARIO:
I have a module called CARs. I have used all five of my lookup fields. So I am looking over the fields and trying to decide which one to get rid of to "make room" for a more important one.
So I finally decided on one to remove (which I really wish I didn't have to), but I can't delete it. I can only send it to the "unused" section because the app has been published. My current clients are in beta so there is no problem removing the field. No important data loss.
The problem is that it seems it still counts against my quota.
Can you please advise? I think a better approach would be to set the quota for "USED" fields.
My vertical app is published, but as I improve and make changes I am running into issues. Specifically with the lookup field limits.
SCENARIO:
I have a module called CARs. I have used all five of my lookup fields. So I am looking over the fields and trying to decide which one to get rid of to "make room" for a more important one.
So I finally decided on one to remove (which I really wish I didn't have to), but I can't delete it. I can only send it to the "unused" section because the app has been published. My current clients are in beta so there is no problem removing the field. No important data loss.
The problem is that it seems it still counts against my quota.
Can you please advise? I think a better approach would be to set the quota for "USED" fields.