Sign Up ›
  • Karen Ishimaru 4
  • NEWBIE
  • 0 Points
  • Member since 2015
  • Chatter
    Feed
  • 0
    Best Answers
  • 0
    Likes Received
  • 1
    Likes Given
  • 1
    Questions
  • 1
    Replies
0 replies

Rich Text fields and Accessibility mode

I work for an agency with blind and visually impaired staff, many of whom rely on Accessibility mode in Salesforce.  The problem we're having: When accessibility mode is ON and you’re in Edit mode looking at a Rich Text field, certain characters (like apostrophes and hard-returns) are converted upon save and subsequently displayed (in Edit mode) as html tags (e.g., <br/>) or html entities (eg, #39 for apostrophe). We’re not sure why Rich Text fields need to behave differently based on whether accessibility mode is on or off.  We tried contacting Salesforce support but were told that this is 'standard functionality' and our best bet would be to post on the Developer's forum.  Wondering if someone from Salesforce's Accessibility team or developer team might be able to get this addressed, or if anyone might have some suggestions.  Thanks!
1 replies

When running a flow as a site guest user, I get a "no such column" error on record lookup

Hi,

I have a Flow created which, after the end user typing a name, performs a record lookup on the Account object, querying on the Account Name.

When I run this as an authenticated user, it works fine.  However as a site guest user, it fails with: 
; nested exception is:
        common.exception.ApiQueryException:
SELECT Account.Id, Account.Name, Account.Second_parent_guardian__c
                                 ^
ERROR at Row:1:Column:34
No such column 'Second_parent_guardian__c' on entity 'Account'. If you are attempting to use a custom field, be sure to append the '__c' after the custom field name. Please reference your WSDL or the describe call for the appropriate names.

caused by element : FlowRecordLookup.Lookup_account

caused by: ; nested exception is:
        common.exception.ApiQueryException:
SELECT Account.Id, Account.Name, Account.Second_parent_guardian__c
                                 ^
ERROR at Row:1:Column:34
No such column 'Second_parent_guardian__c' on entity 'Account'. If you are attempting to use a custom field, be sure to append the '__c' after the custom field name. Please reference your WSDL or the describe call for the appropriate names.
 
 
It shows that one of the attributes "Second_parent_guardian__c" can't be found -- this is a custom field.

I have checked permissions in the Develop --> Sites --> Site Name --> Public Access Settings --> Object Settings --> Accounts --> Field Permissions.  This profile has full read and edit permissions on the field and read permissions on the object.

Also, from the WSDL, it appears to exist: 
<complexType name="Account">
	<complexContent>
		<extension base="ens:sObject">
			<sequence>
			...
				<element name="Second_parent_guardian__c" nillable="true" minOccurs="0" type="tns:ID"/><element name="Second_parent_guardian__r" nillable="true" minOccurs="0" type="ens:Contact"/>
Can anyone please help?  I can't for the life of me work out why this stopped working.  This used to work, but I believe it may have stopped working after the most recent upgrade.

Thanks,
Peter


 
2 replies

named credentials and the mystery of Retry on 401

Deal all,

I have created an integration with an external service (Google) and am using named credentials in this use-case (with a principal user). There is  strange renewal behavior however, that seems quite reproducible:
- if I try to connect after X time (let's say an hour since this is the token window with Google), the first attempt will give an 401 Unauthorized error. 
- if I retry everything works fine 
- looking at the logs, at the named credential it states: Retry on 401 is true
- however, there is no automatic retry on 401, given that a manual second try does make it work...
- this seems to suggest that SF approach to tokens is to not renewal tokens continuesly, but to get one when needed.
- not an illogical concept given the multitenant nature and that some integrations maybe seldom used. However why does this not work then? I also cannot find any documentation on the renewal process exact nature and/or this setting. 
- I am using a Google Auth. Provider over the general one btw (if that has any influence in the backend at all beside preconfig).

Context: this is especially problematic since as a workaround I am now performing a 'dummy' GET request from the service. However that means it limits my max amount of calls to 50 instead of 100. While in theory (but very seldomly) I could get over 100 anyway and I should probably resort to a batch and/or queable apex approach, however this is so rare that it is not in the 80% range of the current implementation. Under normal circumstances I can however get around 50-70 batched calls, and because of the unexpected overhead of the dummy call this is now suddenly a problem... 

There also seems no possibily to check the token renewal date against the current date fow example? But maybe it is not even saved if my theory about the implementation is correct. The only thing I can think of atm is creating an oAuth flow myself and store it in a custom setting, but that would be quite a dissapointing workaround... There is also no possibilty to place the dml outside of the context of the call it seems to me? 

Any help is appreciated! Thanks in advance!