We are having a problem with a custom object (Scholarship) that is tied to Application (another custom object) and Contact. When creating a Scholarship through the Application, we receive the following message:

'Data Not Available The data you were trying to access could not be found. It may be due to another user deleting the data or a system error. If you know the data is not deleted but cannot access it, please look at our support page. '

The interesting thing is that it still creates the Scholarship, but the message is a distraction. I was wondering if anyone else was having a similar issue and if there is a known resolution. Thank you

  • How is an application created, through the standard Salesforce UI or is it a Visualforce page? – greenstork Nov 6 '13 at 17:17
  • Can you perform this action as System Administrator without error? If so you can narrow the issue down to profile security. – Phil Rymek Nov 6 '13 at 17:37
  • We are not having a problem with the application. The issue is with the creation of the scholarship, which is done online through Salesforce. I was able to replicate the issue in a test environment as System Administrator. – user2569499 Nov 6 '13 at 17:42
  • 2
    This isn't nearly enough information to answer this question. Please elaborate with code snippets (triggers, pages, controllers involved, etc), workflow rules, object relationships, etc. We have no way to know what is happening. – Nathan Wallace Nov 6 '13 at 20:57
  • 2
    Please edit your original post with any additional information you provide so everyone can see it. Being honest, what you've just told us, is of little help to me. I recommend you open up the Schema Editor, isolate the three objects, drag them close together, then take a screen shot to post here. – crmprogdev Nov 7 '13 at 20:01

The solution to this issue was a little tricky and would have been impossible to answer without knowing that there was a custom button tied to the Scholarship object. The button was built to bring along the application and student reference as prepopulated fields on the scholarship and take you back to the application once you saved the scholarship. The problem was that there was a contact id hard-coded in the code. Once the code was fixed, the process worked as expected.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.