• Karl
  • 5 Points
  • Member since 2004

  • Chatter
  • 0
    Best Answers
  • 0
    Likes Received
  • 0
    Likes Given
  • 4
  • 6

I am trying to embed some external widgets in a Visualforce page, with no success.  


<apex:page >
    <object codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=5,0,0,0"
    style="WIDTH: 177px; HEIGHT: 125px;" type="application/x-shockwave-flash" data="http://time.gov/widget/NISTtimewidget.swf">
    <param name="movie" value="http://time.gov/widget/NISTtimewidget.swf" />
    <embed src="http://time.gov/widget/NISTtimewidget.swf" type="application/x-shockwave-flash" pluginspage="http://www.macromedia.com/go/getflashplayer">


    <script type="text/javascript" src="http://cdn.widgetserver.com/syndication/subscriber/InsertWidget.js"></script><script type="text/javascript">if (WIDGETBOX) WIDGETBOX.renderWidget('9cbaf4e5-da15-4fff-a1ca-a0fd82c12acc');</script>
    <noscript>Get the <a href="http://www.widgetbox.com/widget/google-search">Google Search</a> widget and many other <a href="http://www.widgetbox.com/">great free widgets</a> at <a href="http://www.widgetbox.com">Widgetbox</a>! Not seeing a widget? (<a href="http://support.widgetbox.com/">More info</a>)</noscript>


Neither of these "widgets" display in the page.  However, I can get the first time widget to display if I use:


<apex:iframe src=” http://time.gov/widget/NISTtimewidget.swf” />

 What am I missting?

  • December 13, 2012
  • Like
  • 0
In an Apex script, I do the following:


Case myCase = [Select
            From Case
            where id = :id];

// the id field in the SOQL where clause is passed into the method

string ownerEmail = myCase.Owner.Email;

The last  line generates the error "Invalid field Email for SObject Name" when trying to compile.  When I try this query in the Sforce Explorer, It shows the relationship as "Name" for Case and Task and you can drill down and see the appropriate results.  But other objects show the relationship for Owner as "User".  I've tried casting to User but that generates an error saying that "Name" is never an instance of "User".

Is this a known issue, and are there any work-arounds?

Message Edited by Karl on 07-07-2008 10:39 AM
  • July 07, 2008
  • Like
  • 0

The Sforce .NET Managed Data Provider is now available on the Sourceforge.net site.  You can go directly to the 1.0 release at:


  • November 17, 2004
  • Like
  • 0
The Name property of the RecordTypeMapping contains the RecordTypeId instead of the Page Layout Name.  Is this a bug?
  • November 16, 2004
  • Like
  • 0
Does anyone know the status of the 2.0 version of the .NET Provider ? There was a presentation on it at Dreamforce, but the sourceforge site still has the 1.0 version.


Bill Emerson
  • November 28, 2005
  • Like
  • 0

How to check which fields that should not be empty in a table in sforce? Example, I get an error when I add a new contact with empty last name. Thanks.


At Dreamforce, there was a demo of a .NET adapter for sForce.  This adapter was to be posted for download a week or so after Dreamforce.  Can someone point me to the link?
  • November 16, 2004
  • Like
  • 0
We'll be using this thread to discuss any possible regressions/issues with the 5.0 release.

    • One thing not mentioned in the release notes, but a change that was made: All IDs should now be returned as 18-character IDs. This was previously not the case, which was a bug as the WSDL defined ID to be 18 characters. If this has affected your integration, please post. Also, if you are doing any special handling for ID fields because their not 18-character you should post this info as well.

      Note that we will be rolling back this behavior for 4.0 and below, and 5.0 will always return 18 character ids. This is only the case for organization_id on the getUserInfo call. Rolled back on 11/15 for 4.0 and below apis

    • Running a query that returns more than batchSize records on OpportunityLineItem is failing. Fixed on 11/15

    • Address Label changes are causing problems for customers using Data Junction and XML/RPC. Please log a case if this issue is affecting you. These labels will be left with their new values.

    • The Web Integration Link URL for the API servers now returns the API pool. For example, this merge field: {!API_Enterprise_Server_URL_25} now returns na1-api.salesforce.com and not na1.salesforce.com. If you have a WIL that needs to return back to the detail page when it's done, you should use the detail page merge field. For example, on Opportunity this would be: {!Opportunity_Link}.

      There are also some scontrols that have stopped working because security settings only allows code to talk with the originating server. We are reverting this change, and a short-term fix is to hardcode the originating server url, such as na1.salesforce.com
      Patched 11/18

    • Calling retrieve when setting the batchSize header and the number of elements retrieved is larger than batchSize is causing unexpected_error faults for some entities. Patched on 11/18. However, there is still an issue if you are selecting a long binary column on an entity such as Attachment or Document. Patch pending

    • Retrieve used to always return id. Now it is only returning id if you request it. Short term workaround: adding id to your select list. Patched 11/18

    • Querying user on firstName or lastName will not return any rows. Patch release on 11/16 to api servers, on 11/18 to all servers.

    • A SOSL call on User that selects division will return an error. Example: FIND {Steve} RETURNING User(Division, Email). Workaround is to not select divison. Patched on 11/18

    • New fields: SystemModstamp was added to AssignmentRule, and SortOrder was added to OpportunityLineItem. New fields can appear in older versions of the API.

    • The WSDL generation page now respects field level security. Note that you must be an admin to even view this page, so you can always make fields hidden via FLS visibile. No change will be made here

    • Dates are now validated such that the year is between 1700 and 4000. This will be rolled back for 4.0 and below, and kept for 5.0. If you are requesting a date field using .NET, and the field is null, .NET turns that into 1/1/1. When sent back up, this is causing problems. This does not seem to be a problem for any other client. Patched on 11/18

    Message Edited by benjasik on 11-18-2004 07:45 PM

    How long does a session last after it goes idle? If some activity is performed periodically within this session time out limit, can the session last indefinitely?