Uploading new version of a File creates system generated post that's visible in all communities via User's "What I Follow" feed

Chatter , Content and Files , Communities , Spring 18

Last updated 2018-03-17 ·Reference W-4696485 ·Reported By 2 users

Fixed - Spring '18 Patch 12.0

When uploading a File via Chatter, the corresponding system generated post or Feed Tracked Change (FTC) has a null value set for the FeedItem record's NetworkScope value.

However, when a new version of the same file is uploaded the NetworkScope value is defaulting to "AllNetworks."

Reference: FeedItem | SOAP API Developer Guide

This in conjunction with the Spring '18, "Follow What You Follow" feature now results in the system generated post for the upload of a new Chatter File version to be visible in the User's "What I Follow" feed in all networks or communities where the user is a member.

Reference: Follow What You Follow

1. Navigate to the user's Chatter Feed.

2. Select the File action in the Chatter Publisher and "Upload a file from your computer"

3. Now in the corresponding File post or FeedItem in Chatter, select the "More Actions" picker and "Upload New Version" | Browse... select the same file or a new one | Upload New Version.

4. Navigate to your community and open the user's Chatter Feed.

Actual Results: With "Follow What You Follow" (Follow Model v2 enabled), uploading a new file version created a system generated feed tracked change (FTC) post that's visible externally in communities where the user is a member despite the File being uploaded internally.

Expected Results: When uploading a new File version the corresponding FTC post would maintain the same visibility as the FeedItem or post for the original File.

You may contact Salesforce Support via a Case to request disabling the Spring '18 "Follow What You Follow" feature.

See the Knowledge Article, "See more relevant information in your Chatter feed" for more details and please reference it when contacting Support:


Reported By (2)

Is it Fixed?

AP0 AP3 AP4 AP5 AP6 AP7 AP8 AP9 AP14 AP15 CS1 CS2 CS3 CS4 CS5 CS6 CS7 CS8 CS9 CS10 CS109 CS108 CS107 CS106 CS105 CS102 CS101 CS100 CS115 CS11 CS116 CS12 CS137 CS138 CS13 CS14 CS15 CS16 CS17 CS18 CS19 CS20 CS21 CS22 CS23 CS24 CS25 CS26 CS27 CS28 CS30 CS31 CS32 CS33 CS40 CS41 CS42 CS43 CS44 CS45 CS47 CS50 CS51 CS52 CS53 CS54 CS57 CS58 CS59 CS60 CS61 CS62 CS63 CS64 CS65 CS66 CS67 CS68 CS69 CS70 CS71 CS72 CS73 CS74 CS75 CS76 CS77 CS78 CS79 CS80 CS81 CS82 CS83 CS84 CS85 CS86 CS87 CS88 CS89 CS90 CS91 CS92 CS93 CS94 CS95 CS96 CS97 CS98 CS99 EU1 EU4 EU6 EU7 EU8 EU9 EU10 EU12 EU13 EU14 EU15 EU16 EU17 EU18 EU19 NA8 NA21 NA29 NA32 NA33 NA34 NA37 NA38 NA39 NA40 NA42 NA44 NA45 NA46 NA47 NA48 NA49 NA50 NA51 NA52 NA53 NA54 NA55 NA56 NA57 NA58 NA59 NA60 NA61 NA62 NA63 NA64 NA65 NA66 NA67 NA68 NA69 NA70 NA71 NA72 NA73 NA74 NA75 NA76 NA77 NA78 NA79 NA80 NA81 NA82 NA83 NA84 NA85 NA86 NA87 NA88 NA89 NA90 NA91 NA92 NA93 NA94 NA95 NA96 NA99

Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.