I'm hitting a brick wall here.  When a non-admin users tries to send a tweet with the new update, they get

No such column 'id' on entity 'sf4twitter__Twitter_Credentials__c'. 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. In this instance, it is not visible to the user because the custom object has not yet been deployed

As an admin, I can't even see an object with this name.  The user themselves has full access to all the Twitter related custom objects.  We're not using Twitter Contributors, nor do we have a need for that.

Is this an Object, or a Custom Setting?  Why would it be completely hidden from Admin view?

The objects I see, as an admin, are

Twitter_Account__c

Twitter_Contributor__c

Twitter_Follower__c

Twitter_Search__c

Twitter_Scheduler__c

Twitter_Credentials__c isn't even listed on the app's install page under View Installed Packages in the setup area.

Please help...

Whenever we run a manual "Get more Conversations" in the Twitter for Salesforce app for our Twitter Account we getting this error: Insert failed. First exception on row 0; first error: INVALID_PERSON_ACCOUNT_OPERATION, cannot reference person contact: [], Code Line:436

We have Person Accounts enabled in our org and it pulls in Twitter Searches fine - just not messages to our Twitter Account.

We have the lastest version of SF for Twitter installed - 4.2.12 - anyone know of a fix for this? Thanks!

We can't post to our Facebook page with the Salesforce for Facebook app. We get a message "Argument cannot be be null." It works if we post to Twitter. Here's a screenshot of what we are seeing:

Trying to install Salesforce For Facebook & Twitter into Full-Data Sandbox environment, but following issue encountered:

Note: All Validation Rules have been made in-active, all workflow rules are in-active. 

Have previously installed the package successfully in other sandbox environments without problem.

Your request to install package "Salesforce for Social Media R 4.2.2 2011.05.11" was unsuccessful. None of the data or setup information in your salesforce.com organization was affected.
If your install continues to fail, contact Salesforce CRM Support through your normal channels and provide the following information.
Organization: XXXXXXXXXXXXXXX (XXXXXXXXX)

User: XXXXXX XXXXXXXX (XXXXXXX)

Package: Salesforce for Social Media (04tA0000000EstHIAS)
Problem:
1. Apex Classes(01p20000000Edbw) testtriggers.testTwitterTestTriggerOnBeforeInsertUpdate()System.AssertException: Assertion Failed(sf4twitter)External entry point

Validation Errors While Saving Record(s)
There were custom validation error(s) encountered while saving the affected record(s). The first validation error encountered was "00DP00000008s9N: APEX_TEST_FAILED [01p20000000Edbw: testtriggers.testTwitterTestTriggerOnBeforeInsertUpdate(): System.AssertException: Assertion Failed(sf4twitter)External entry point]".

I have implemented Salesforce For Facebook and Twitter v4.

I have a requirement to hold the Facebook Id against more than one customer (Account), however, there is a check for duplicates built into the installed package.

Is there any way to disable this?

Does this application only work correctly with Fan Pages and won't synch with Individual Facebook pages???

Other than the fact that the app installs successfully, there are some serious troubleshooting issues with the Salesforce for Twitter 2.0 app. In attempting to get the app working for a client using Enterprise Edition. I've been running into several usability roadblocks that are requiring some serious revers-engineering.

To date, the most worrisome issue is the fact that the "Troubleshooting" link within the app (located on the right column of the Salesforce for Twitter" homepage). Other issues I will articulate below.

I'm hitting a brick wall here.  When a non-admin users tries to send a tweet with the new update, they get

No such column 'id' on entity 'sf4twitter__Twitter_Credentials__c'. 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. In this instance, it is not visible to the user because the custom object has not yet been deployed

As an admin, I can't even see an object with this name.  The user themselves has full access to all the Twitter related custom objects.  We're not using Twitter Contributors, nor do we have a need for that.

Is this an Object, or a Custom Setting?  Why would it be completely hidden from Admin view?

The objects I see, as an admin, are

Twitter_Account__c

Twitter_Contributor__c

Twitter_Follower__c

Twitter_Search__c

Twitter_Scheduler__c

Twitter_Credentials__c isn't even listed on the app's install page under View Installed Packages in the setup area.

Please help...

The request to twitter failed. Failed to parse XML due to: only whitespace content allowed before start tag and not F (position: START_DOCUMENT seen F... @1:1)| An error occurred for this search: [id : a0O300000027JzrEAE, page : 0]
The request to twitter failed.
System.HttpRequest[Endpoint=https://twitter.com/statuses/user_timeline.xml?since_id=19360744679&count=99&page=0, Method=GET]
System.HttpResponse[Status=Unauthorized, StatusCode=401]
Twitter returned the following message while performing this action: Twitter error code: 401, Twitter Error Message: Invalid / used nonce. Please review Twitter error messages at http://apiwiki.twitter.com/HTTP-Response-Codes-and-Errors  and check Twitter’s system status at http://dev.twitter.com/status

Also, when I try to delete and readd the Twitter account, I get this when trying to regrant OAuth

The request to twitter failed. Failed to parse XML due to: only whitespace content allowed before start tag and not F (position: START_DOCUMENT seen F... @1:1)

This started over the weekend, without anything being touched.  We had some scheduled jobs set to run every 10 minutes to grab tweets related to a single Twitter account, and it was working fine for about 4 days.  Now, we're completely stuck, and having to revert back to using CoTweet.

You have this page talking about pulling relevant content from Facebook and Twitter,

http://www.salesforce.com/chatter/facebook-twitter-integration/

So...where is the Facebook and Twitter feature set n Chatter?  How is it enabled?  Where do we setup FB and Twitter account info?  The screenshot seems to indicate that the FB connect is on the profile page, but...it's not.  It also seems to indicate that the Twitter integration that already exists (and creates cases) is included/enhanced.  Is this going to be (near) real time, or is it still based on a manual refresh?

Is the "you'll leverage" wording on this page hinting that this isn't available?  If so, shame shame on your marketing folks.  There's no flashy "safe harbor" statement on this page...:)

Cheers,

/p

See last paragraph for summary...

I was trying to create an adaptive loader routine in Apex Code, and I came across an interesting bug. First, let's take a look at what I was attempting to do:

sobject record = cache.load( recordId );
set< id > relatedIds = new set< Id >( );

for( SObjectField field: Cache.getFieldTokens( record.getSObjectType( ) ) ) {
   if( record.get( field ) != null && record.get( field ) instanceOf id ) {
       relatedIds.add( Id.valueOf( record.get( field ) );
   }
}
map< id, sobject > related = new map< id, sobject >( Cache.load( relatedIds ) );

Where:

* Cache.load( Id ) returns a single record from a static map, querying the record, if necessary.

* Cache.getFieldTokens( SObjectType ) returns all tokens from a SObjectType.getDescribe().fields.getMap().values(), again loading from a static map if previously defined.

* Cache.load( Set< Id > ) is a batch version of above, returning a list of SObject records in arbitrary order, querying records that are missing from the cache, and capable of returning multiple types of SObjects.

When I tried this initially, I got an odd exception: "Invalid ID."; the exception was thrown from my Cache class, so I wondered how it could have gotten there.

I fiddled around with the straightforward means of assigning an ID via a string:

Id a = '0013000000f3adA'; // OKAY
Id b = 'john doe';        // EXCEPTION

So, it would appear the setter function works fine.

Next, I tried casting:

String a = '0013000000f3Adf', b = 'john doe';
Id c = ( Id )a; // OKAY
Id d = ( Id )b; // EXCEPTION

So far, so good; it's also using the setter function of ID.

Next, I tried using Id.valueOf:

Id a = Id.valueOf( '0013000000d3afA' ); // OKAY
Id b = Id.valueOf( 'john doe' );        // OKAY ?!?!

This means that Id.valueOf doesn't use the setter method, but instead internally constructs an ID.

The next tidbit came when I tested the Set<T> class against an ID.

First, a straight assignment:

Set< Id > a = new set< Id >( );
a.add( '00130000003faZs' ); // OKAY
a.add( 'john doe' ); // EXCEPTION

So, it seems that Id's setter is in play here.

Next, I tried using the defunct valueOf:

Set< Id > a = new Set< Id >( );
a.add( Id.valueOf( 'john doe' ) ); // OKAY ?!?!

So, it seems that a "corrupted" ID value will be accepted into a set of IDs.

This led to the next problem:

for( Id b: a) {
  // Do something
}

If a is a set of IDs, and a corrupted ID value (via valueOf) is in the set, you will receive an "invalid ID" error here.

Finally, this led me back to my source code:

if( Id.valueOf( 'john doe' ) instanceOf Id ) {
  System.debug('** Invalid ID was accepted by instanceOf **');
}

So, Set<T>.add(Object) apparently checks the class of the incoming object against the class of its template, and automatically accepts them without question, otherwise attempts a cast (calling the correctly-working setter function).

I submitted a case to support, and they told me to go away because I don't have premier support, and all I wanted to do was log a bug with the dev team.

Hopefully an admin will see this and it will get logged as a bug. In the interim, the community should note that Id.valueOf is broken, and instanceOf is also broken as a side-effect. Instead, you should always use casting, and try-catch the cast so you can detect incorrect ID values.