You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 17, 2023. It is now read-only.
The ForcePad app for iPad isn't handling two of our client's custom objects properly. The first object is called VC Investment, and includes a Master-Detail field as well as a Lookup field, both pointing to Accounts There are two related lists being used for this object at the Account level; VC Backing, and VC Investments. The VC Backing field shows up just fine in the App, but the VC Investments list doesn't. Instead, it drops you into VC Backing again.
The second object is called Board Member, and has the same issue on ForcePad. This is another object with a Master-Detail relationship.
Thanks in advance!
Don Snider
Force by Design
The text was updated successfully, but these errors were encountered:
Hiya, I wrote ForcePad. Sorry to hear you're having trouble. :/
Sounds like there might be an issue here with multiple related lists that point to the same object. Unfortunately I'm no longer at Salesforce and ForcePad is now out of my hands. I don't know that there will be any more updates, but perhaps you'd be willing to contribute a fix to this repo?
Hello,
The ForcePad app for iPad isn't handling two of our client's custom objects properly. The first object is called VC Investment, and includes a Master-Detail field as well as a Lookup field, both pointing to Accounts There are two related lists being used for this object at the Account level; VC Backing, and VC Investments. The VC Backing field shows up just fine in the App, but the VC Investments list doesn't. Instead, it drops you into VC Backing again.
The second object is called Board Member, and has the same issue on ForcePad. This is another object with a Master-Detail relationship.
Thanks in advance!
Don Snider
Force by Design
The text was updated successfully, but these errors were encountered: