#Unofficial Salesforce0 debatiendo

I think I know the answer to this, but wanted to validate.  The Quick Choice component that is now in the Flow Base Pack is different than the "old" Quickchoice FSC component.  Is that correct?  The primary reason for the ask is that I am trying to do some org clean up on Apex Classes, etc and some classes attached to the Quickchoice FSC component is causing some deployment issues. 

I should be able to remove that old Quickchoice component without any issues, correct? 

Hi Guys, would like to contribute and pay something back to community.

Did develop lovely lwc component that based on inputed collection showing Gantt like chart.

Pls let me know how I can make it available to community.

Thx!

Petr

Blog article on the power of Flow for user process guidance and the user of installable Flow Screen Component and Flow Actions. And it's so "easy" now (compared to anything else anyway). #AlwaysBeLearning  See how installable flow screen components can make your life so much easier and give great user experiences. https://mighyforce.dreamhosters.com/2020/12/meta-flow-a-new-level-of-productivity-alwaysbelearning/ @Alex Edelstein #Flow #Flow Builder #Screen Flow #Unofficial Salesforce #Unofficial DataTableFSC @Eric Smith 

Hello all,

Would it be possible to add 2 files (they are always the same) to a case, when creating a case in a flow?

I don't want to have the add files button https://unofficialsf.com/flow-and-file-upload/

But maybe i can use this someway?

or are there other ideas?

Can i upload those files as static resources and use them in the flow?

Any ideas are welcome :)

thanks in advance.

I created a new Idea for being able to generate our own error messages in declarative automation. Add your thoughts there about how it should work!

Idea: Error/Problem Raising in Declarative Automation

What's the best way with declarative automation to update the records on the other side of a junction object? For instance, if a change is made to an Opportunity, update a field on all Contacts related to that record via an OpportunityContactRole. You can't do this with Process Builder. I also don't believe there is a way to cleanly (i.e., without DML actions within a loop) to get all the IDs of those Contacts in a way that Flow can make a single query for them all. For instance, it would be great if we could query for all OpportunityContactRoles, loop through those and put their Contact IDs in a new collection, then use that collection in a new query for all the Contacts, but that isn't an option, right? Is there a good way, perhaps using one of the #Unofficial Salesforce components (https://unofficialsf.com/flow-resources/)? Would I have to create a string out of the Contact IDs and pass those into apex that can use that in query criteria? At that point I'd probably rather just create an apex trigger instead of trying to hack together multiple technologies.

Hi @Alex Edelstein 

I saw the note in GitHub > Issues that richTextInputFSC broke with Winter 20 and a new version was posted. When I tried to install it, I got the attached error message. I am trying to fix a critical issue and hoping to have a version I can put in production. The version off unofficialsf.com is still the old one that doesn't work with Winter 20.