• Jean Luc Raes
  • 0 Points
  • Member since 2014

  • Chatter
  • 0
    Best Answers
  • 0
    Likes Received
  • 1
    Likes Given
  • 0
  • 2
Performing the first Challenge of this Superbadge for APEX, I am receiving the below error. But it is not true because the Maintenance Request does indeed have all of the attributes cited when I try via the GUI and via a Test Class. Can someone please tell me what is wrong?

Challenge Not yet complete... here's what's wrong:
Inserting a new Maintenance Request of type 'Routine Maintenance' and then closing it did not create of a new Maintenance Request based upon the original record correctly. The challenge is expecting to find the closed Maintenance Request plus an 'New' Maintenance Request of type 'Routine Maintenance' with the same Vehicle as the closed one.

(Also, the challenge didn't specifically mention that the Case and Product2 objects should be relabeled)

I am developing an application in Lighting, The functionality of that app is sending a file to Amazon s3 for that I am using AJAX after choosing a file from input type file in HTML, But lighting is not allowing me to connect to Amazon S3. I am getting below error message in console.
Refused to connect to 'https://s3.amazonaws.com/CloudFilesDemo/' because it violates the following Content Security Policy directive: "connect-src 'self' https://api.bluetail.salesforce.com https://staging.bluetail.salesforce.com https://preprod.bluetail.salesforce.com".

statusText: "SecurityError: Failed to execute 'open' on 'XMLHttpRequest': Refused to connect to 'https://s3.amazonaws.com/CloudFilesDemo/' because it violates the document's Content Security Policy

Could you please suggest me anyway to achieve this.


Since last week we started having problems running SOQL queries on a custom Big Object.
Executing the SOQL in our sandboxes gives no problem at all.
So querying/exporting data from Dataloader, Workbench and Execute Anonymous session all give the same error, immediately after the request is fired: "UNKNOWN ERROR: [REQUEST_RUNNING_TOO_LONG] Your request was running for too long, and has been stopped"