Heya Gary, dude just want to say again thank you for these videos. I am considered a intermediate/senior Dev and I often refer to your videos just to make sure I know what I am talking about. I would love to hear your thoughts on how to jump ahead of the curve on the AI wave that is hitting Salesforce right now and how, as a developer, you can learn how to implement complicated AI solutions in Salesforce :)
Thanks man I'm glad you liked it! Thanks for havin me on the podcast the other day! I'm lookin forward to the episode! Thanks for all you do for the community as well!
Matt - I have a question, In AccountService accepting set of accountids, instead of returning a list of value result, returning a single record value. How this will be handled from trigger?
I'd love to hear your thoughts on re-usability for declarative automation as well. For example, if I have Flows and Apex that need to use the business logic in your example (ProjectedOppProfits), how should I structure that? Is it easiest to make a second identical method in AccountService that is usable as a Flow Apex action (ie. not bulkified)?
It depends on who you ask to an extent I think and your use case. Personally, if I intend to leverage flows (or find I should leverage a flow in the future) I just make the method invocable and design the flow to think in bulk instead of single records.
Not sure why I decided that I would say Apex Commons instead of just Apex Common... It's just the Apex Common Library. Please forgive me, lol.
1. Presentation Layer -- UI(LWC,Aura)
2. Service Layer -- business logic
3. Domain Layer -- Triggers and default logic
4. Selector Layer -- for Data access(fetch)
the presentation layer is use just for the component (js,html,css) or the controllers too?
Heya Gary, dude just want to say again thank you for these videos. I am considered a intermediate/senior Dev and I often refer to your videos just to make sure I know what I am talking about. I would love to hear your thoughts on how to jump ahead of the curve on the AI wave that is hitting Salesforce right now and how, as a developer, you can learn how to implement complicated AI solutions in Salesforce :)
I'm so thankful with your videos and learning with you :)
Really interesting, loooking forward to the Series. Would like you to bring out the difference between Domain and Service layer.
I'm gonna do my best! Hopefully it'll all make sense afterward!
Great video
good stuff matt!
Thanks man I'm glad you liked it! Thanks for havin me on the podcast the other day! I'm lookin forward to the episode! Thanks for all you do for the community as well!
Excellent,It would be great if you could bring Apex mocks as well into the picture and have a deep dive into Apex commons
Absolutely, we will definitely be covering that. It'll be covered in the last two episodes of this series. Episode 10 and 11.
@@CodingWithTheForce Brilliant That you have an entire series.
Thanks!
Matt - I have a question, In AccountService accepting set of accountids, instead of returning a list of value result, returning a single record value. How this will be handled from trigger?
Can you please upload a video on how to query case and case history object and update case based on last modified user in a batch class
Hey probably not a question related to the video ... but can we choose a specific fields to be fetched from a cross org adapter ....
Waiting for the second tutorial in Apex commons.
It's comin, I promise! Technically the next five episodes are done I'm just trying to finish them all and release the whole series at once.
@@CodingWithTheForce Oh that's brilliant.
I'd love to hear your thoughts on re-usability for declarative automation as well. For example, if I have Flows and Apex that need to use the business logic in your example (ProjectedOppProfits), how should I structure that? Is it easiest to make a second identical method in AccountService that is usable as a Flow Apex action (ie. not bulkified)?
It depends on who you ask to an extent I think and your use case. Personally, if I intend to leverage flows (or find I should leverage a flow in the future) I just make the method invocable and design the flow to think in bulk instead of single records.
When you say that with declarative configuration, Salesforce takes care of most of the Separation of Concerns for you, can you elaborate on that?