• Artie B
  • NEWBIE
  • 35 Points
  • Member since 2014
  • CTO
  • Haka Products

  • Chatter
    Feed
  • 1
    Best Answers
  • 1
    Likes Received
  • 1
    Likes Given
  • 3
    Questions
  • 5
    Replies
Hi,
User-added image


we were developed an managed App.we used two Permission sets (API names like XXXXX_Admin,XXXXXX_User ).when we installing this app in Partner enterprise edition ,it is working fine.But we got the above error while installing in Enterprise Edition (Both Sandbox and Production)


Can Any one Help us...!!!
In Winter '16 pre-release on gs0, the renditionUrl property is not properly populated when accessing an instance of ConnectApi.ContentCapability in Apex. This works fine in Summer '15 and previous.  

I'm reporting this here in the hopes that somebody from Salesforce will read this (since my Case was closed).
I have a VF page that I am using as an inline page on the Opportunity detail page layout. It retrieves and displays files (FeedItems with ConnectApi.ContentCapability) from Chatter feeds on records related to the Opportunity. After making the page available for mobile, it will display within the Salesforce1 mobile app. However, there are two URLs returned with the ContentCapability class that wraps the Chatter File, downloadUrl and renditionUrl, that apparently don't work within the mobile container. The following VF, where file is a reference to an instance of ConnectApi.ContentCapability renders fine on the desktop (and in /one/one.app, incidentally), but the image does not display in the mobile app, nor does the the download link work. The title attribute works just fine.
 
<div class="col-xs-6 col-sm-3 col-md-2">
    <a href="{!file.downloadUrl}" class="thumbnail">
        <img src="{!file.renditionUrl}" />
    </a>
    <div class="captionContainer">
        <h6>{!file.title}</h6>
    </div>
</div>

Is there a way to "convert" these URLs to something that SF1 would understand...or do I need to use the Chatter REST API or some other method to fetch these URLs when the page is running in the mobile context?

The downloadUrl looks like

https://c.na17.content.force.com/sfc/servlet.shepherd/version/download/068o0000000wrG3?asPdf=false&operationContext=CHATTER

and the renditionUrl looks like

https://c.na17.content.force.com/sfc/servlet.shepherd/version/renditionDownload?rendition=THUMB720BY480&versionId=068o0000000wrj0&operationContext=CHATTER&contentId=05To00000009kkc

Thanks,

Artie
I have created a feed-based layout in my dev org. This layout has a VF page as a custom component on the Feed View section of the layout. When I attempt to deploy it to the packaging org for our managed package, the deploy fails with "Error: Not a valid custom component".

While investigating, I attempted to manually create a new feed-based layout on this same custom object in the packaging org. I was able to create the layout, but when I attempted to add a VF page to the Feed View, the VF page picker fails to "find" any of my pages. I can add the VF page to the "Details" section (the main part of the layout). It would appear that the Feed View custom component is broken for packaging orgs (those with a namespace). Can anybody confirm/deny and/or point me to the documentation for this?
I have a VF page that I am using as an inline page on the Opportunity detail page layout. It retrieves and displays files (FeedItems with ConnectApi.ContentCapability) from Chatter feeds on records related to the Opportunity. After making the page available for mobile, it will display within the Salesforce1 mobile app. However, there are two URLs returned with the ContentCapability class that wraps the Chatter File, downloadUrl and renditionUrl, that apparently don't work within the mobile container. The following VF, where file is a reference to an instance of ConnectApi.ContentCapability renders fine on the desktop (and in /one/one.app, incidentally), but the image does not display in the mobile app, nor does the the download link work. The title attribute works just fine.
 
<div class="col-xs-6 col-sm-3 col-md-2">
    <a href="{!file.downloadUrl}" class="thumbnail">
        <img src="{!file.renditionUrl}" />
    </a>
    <div class="captionContainer">
        <h6>{!file.title}</h6>
    </div>
</div>

Is there a way to "convert" these URLs to something that SF1 would understand...or do I need to use the Chatter REST API or some other method to fetch these URLs when the page is running in the mobile context?

The downloadUrl looks like

https://c.na17.content.force.com/sfc/servlet.shepherd/version/download/068o0000000wrG3?asPdf=false&operationContext=CHATTER

and the renditionUrl looks like

https://c.na17.content.force.com/sfc/servlet.shepherd/version/renditionDownload?rendition=THUMB720BY480&versionId=068o0000000wrj0&operationContext=CHATTER&contentId=05To00000009kkc

Thanks,

Artie
After the Winter'16 upgrade of my dev org, I have set up some custom metadata types for my application. I found a bug with Checkbox field in Custom Metadata type that if the field name is greater than 19 characters (excluding namespace and __c) then the SOQL always return false value for that field. The UI displays the value correctly but the query returns always false.

If you have started using custom metadata types then please try this in your org and share the results.
I have a VF page that I am using as an inline page on the Opportunity detail page layout. It retrieves and displays files (FeedItems with ConnectApi.ContentCapability) from Chatter feeds on records related to the Opportunity. After making the page available for mobile, it will display within the Salesforce1 mobile app. However, there are two URLs returned with the ContentCapability class that wraps the Chatter File, downloadUrl and renditionUrl, that apparently don't work within the mobile container. The following VF, where file is a reference to an instance of ConnectApi.ContentCapability renders fine on the desktop (and in /one/one.app, incidentally), but the image does not display in the mobile app, nor does the the download link work. The title attribute works just fine.
 
<div class="col-xs-6 col-sm-3 col-md-2">
    <a href="{!file.downloadUrl}" class="thumbnail">
        <img src="{!file.renditionUrl}" />
    </a>
    <div class="captionContainer">
        <h6>{!file.title}</h6>
    </div>
</div>

Is there a way to "convert" these URLs to something that SF1 would understand...or do I need to use the Chatter REST API or some other method to fetch these URLs when the page is running in the mobile context?

The downloadUrl looks like

https://c.na17.content.force.com/sfc/servlet.shepherd/version/download/068o0000000wrG3?asPdf=false&operationContext=CHATTER

and the renditionUrl looks like

https://c.na17.content.force.com/sfc/servlet.shepherd/version/renditionDownload?rendition=THUMB720BY480&versionId=068o0000000wrj0&operationContext=CHATTER&contentId=05To00000009kkc

Thanks,

Artie
Hi,
User-added image


we were developed an managed App.we used two Permission sets (API names like XXXXX_Admin,XXXXXX_User ).when we installing this app in Partner enterprise edition ,it is working fine.But we got the above error while installing in Enterprise Edition (Both Sandbox and Production)


Can Any one Help us...!!!
Hi,

The Spring '14 Release Notes state "Starting Spring ‘14, ISVs can delete the following types of components when updating a previously released managed package" and lists Custom Fields as one of the options.

They also state "You can delete managed components, both declaratively, from the user interface, and programmatically, using the Metadata
API."

However when I log into the release account of our managed package, and view package components, there is no option in the Actions column to delete the custom fields from the package. We are an ISV partner so how do we delete fields through the user interface?

Thanks!
After the Winter'16 upgrade of my dev org, I have set up some custom metadata types for my application. I found a bug with Checkbox field in Custom Metadata type that if the field name is greater than 19 characters (excluding namespace and __c) then the SOQL always return false value for that field. The UI displays the value correctly but the query returns always false.

If you have started using custom metadata types then please try this in your org and share the results.