Calculated Fields Populating Date depending on Type

Hi Richard Owen

Lemme save your time on explorations of unary operations.



On the video - the Opp name receives Meeting the start date (keeping the original name in place) on meeting type is set to "assessment" and, as you can see, an Opp name refreshes automatically on the start date change.

Unlike the read-only calc field, this configuring approach keeps an enriched Opp name editable for the users (zoom in the screenshot to read it)





Let me know the name of the Opp field you like to put the start date - I will adjust the logic to put the value in your field with Logic Builder and upload here a ready-to-use solution within 15 min :)

thank you. field name is "Assessment Date" and this will be a date field. 

Richard,
what is the custom field name (that ends with _c)?  assessment_date_c ?

Hi 

assessment_c

Richard

And here is zip file to install via Module Loader
z20210316_flowchart_lb605092c65b1e86_88031912.zip

I test it out on sg-examples1.demo.sugarcrm.eu/.../asdf) with 2 custom fields
Meeting.meeting_type_c and Opportunity.assessment_c

Please drop a line if this works

Please note that Meeting.StartDate is visualized in user's time zone as DateTime type field , but the value is stored in database in UTC, while "time zone" is not applicable to Date type field .
Therefore, if to assign DateTime to Date field , then the date will be taken from UTC datetime value.
In case of some particular time zone should be taken into account, I would suggest to include the shift into the logic - let me know

Sorry I need a no code solution
Getting a syntax error?

ifElse,related(equal($meetings,meeting_type_c,"assessment"),related($meetings,"date_start"))

Sorry I need a no code solution
Getting a syntax error?

ifElse,related(equal($meetings,meeting_type_c,"assessment"),related($meetings,"date_start"))

The correct syntax may be this one:

ifElse(equal(related($meetings,meeting_type_c), "assessment"),related($meetings,"date_start"),date())

Sorry, but this is a purely a no-code solution - literally, no one was forced to write a line of PHP code to get a solution to work.

When Module Builder's Studio is employed, then the "Deploy" button is clicked, Module Builder creates a zip package and installs it via Module Loader automatically - that is configuring with no code too.

If a teammate or a colleague asks for a custom module, is there any other way than to provide a zip package generated with Module Builder?

Unlike Module Builder, the cloud tool Logic Builder is not included in Sugar therefore XSS (Cross-Site Scripting) security prevents automatic installation- the generated zip should be installed manually - so the difference is just in the deployment procedure.

In both cases, there are no reasons to look into the code packed in the package to benefit from the results

I hope this makes sense.

Sorry we do not allow module uploads into our system 

Hi Andre, sorry still has the same Error. Will work on another way.

I think André Lopes's formula is just missing quotes around the field name: "meeting_type_c". 

ifElse(equal(related($meetings,"meeting_type_c"), "assessment"),related($meetings,"date_start"),date())

instead of 

ifElse(equal(related($meetings,meeting_type_c), "assessment"),related($meetings,"date_start"),date())

Take a look at:

https://support.sugarcrm.com/Knowledge_Base/Studio_and_Module_Builder/Sugar_Logic/Sugar_Logic_Walkthrough_Related_Module_Formulas/

You are right Francesca Shiekh

I didn't notice that!

Hi
Getting:

date: Requires exactly 1 parameter(s)

so still not working?

Check the syntax, the formulas can be a bit tricky and it's hard for us to test since we don't have your custom fields, I think the two conditions have to be tested separately and put into an and statement.

ifElse(and(equal(related($meetings,"meeting_type_c"), "assessment"),equal(related($meetings,"date_start"),date())))

My corrections may still not work, and you might need to put some effort into finding what is wrong.

At its basic André's solution shows you how to reference fields in related modules. Which is the first clue to achieve what you need.

There is some guidance here to help you structure it but 

ttps://support.sugarcrm.com/Knowledge_Base/Studio_and_Module_Builder/Sugar_Logic/