• gitu
  • NEWBIE
  • 0 Points
  • Member since 2012

  • Chatter
    Feed
  • 0
    Best Answers
  • 0
    Likes Received
  • 0
    Likes Given
  • 1
    Questions
  • 6
    Replies

I learned something interesting accidentally today. It seems if you revoke "Manage Users" permission from a user, he/she cannot see "Federation Id" field either. Is this documented anywhere? Are there other fields that are hidden due to permissions?

  • October 27, 2012
  • Like
  • 0
My non-profit is using salesforce to manage our donors. Several donors contribute more than once a year, and we need to track each one of thier donations by date and amount, not just their largest annual/first/last donation. How can we be sure to track every donation under each contact?

Hi,

 

We implemented OAuth 2.0 using Web Server Authentication Flow. It was working fine in October/November but all of a sudden it has stopped working. Whenever we try authorising a new client the server return (400) Bad Request with the body

 

{"error":"unsupported_grant_type","error_description":"grant type not supported"}

 

grant_type is set as authorization_code which is definitely valid.

 

Is there any reason why OAuth would suddenly stop working?

 


This is how we have implemented OAuth:

 

First user is directed to: https://login.salesforce.com/services/oauth2/authorize?response_type=code&client_id=blah.id&redirect_uri=https://domain.com/Web/Salesforce/Callback.aspx&scope=api%20refresh_token

 

User is prompted by Salesforce to login to their account.

 

Once user is authenticated Salesforce calls Callback.aspx, Callback.aspx requests refresh token on behalf of the client by making a POST request to: https://login.salesforce.com/services/oauth2/token with the payload:

grant_type=authorization_code&code=blah.code&client_id=blah.Id&client_secret=11111111&redirect_uri=https://domain.com/Web/Salesforce/Callback.aspx

 

Content type is definitely: application/x-www-form-urlencoded

 

Many thanks,

Hi

 

I am using a formula-

if( checkbox__c =true, DateTime__c- CreatedDate , now()-CreatedDate )

 

When I click ''Check Syntax' button then there is no error andCompiled sise is 207 characters, but when I tried to save it, this is showing error "Formula(s) that reference this field are no longer valid: Compiled formula is too big to execute (16.122 characters). Maximum size is 5.000 characters".

This is very basic and small formula, I wonder why this is showing error.

 

 

I'm looking at an org where there is no relationship between Accounts and Cases. I have never seen that before. It's professional edition, which I have as well so I'm comparing my org to there org and I can clearly see that under Cases my org has the Account lookup and theirs does not.

 

Has anyone ever seen this before? If so, how is this even possible to do inside Salesforce. More importantly, why would you do that?

 

 

  • October 19, 2012
  • Like
  • 0

Hai,

 

Am ne to cloud i have a partner portal user. he has full access to all

sobjects. But i want to restrict some records from my users

to partal. IS it possible to setting role hierarchy?

 

Any one please help me.

 

 

Thank you

 

What's the correct way to create a field that should not change after the record is created?

 

I see that there is an ISCHANGED() function for validation rules.  Should I just create a validation rule that sees if any of these fields have been changed?  Should I make the fields read-only?  Will either of those techniques prevent Apex code launched by a user from creating new records?

 

I'm guessing that a validation rule is more efficient than a trigger.

 

The fields are used as foreign keys to an external database, and need to be immutable.  Not even an administrator should be able to edit the field.