Thank you for attending my Design Time session on July 12th! Below are the unanswered question from the chat - please let me know if you have any other thoughts!
I have also bolder areas where I need more clarification, so if you submitted that question, please share more details!
----
We're unable to identify where the SFM is currently used (tied to lack of versioning somewhat)
You can’t assign the SFM directly - you need to get out from this form.
It doesn't warn is you're trying to do something that is not fully supported on all platforms.
When you are filtering/qualifying it's very easy to inadvertantly modify a filter that's used elsewhere.
Will the pop up indicating impacted areas show up on delete only or on update as well?
Doesn’t compatible with different Data Types - it takes only related text to text or number to number
Fields referenced in SFM formulas and validation rules need to be on the layouts.
Will using Formula fields still be a restriction on a layout?
How about a validate button plus on save? both/and?
Maybe a daily check with email alerts? The validate button idea is a good idea IU-wise.
It would be good to dig into the field validation in the SFM.
Will errors on sfm be very clear?
Usually when field is removed or changed, sfm throws unknown error instead of telling clearly what the error is.
If we changed the naming convention how would that impact existing?
Can we get a time/date user modified stamp on the expressions?
If we time/date user stamp edits to the SFM at the SFM level itself, can we get a snippet of exactly what component or expression was modified?
Can we see audit trail also - if we modify expression?
Top 2 Pain-points
1. Performance Poor - On load, On Save
2. Cannot track version(Audit trial) - Who, When & what was modified for each component
3. Bottom-up approach
4. Debugging is difficult - Cannot trace to error cause
Didn’t open the SFM properly - get the 101 error or View state error...
Can we see all kind of fields or any restrictions?
Can we see SFDC formula fields in the SFM page layouts?
Can we show errors of validations directly while entering the value instead of save button now?
It would be good to show the mapped field when hovering over the field on the SFM page layout.
Will using Formula fields still be a restriction on a layout?
Maybe a daily check with email alerts?
Will we be able to clear the value in a field (set to Blank) in the mapping....today we cannot set a value of blank..?
Need to map NULL. Right now we have to use SFM formulas to null values
Can we map fields not on the page layout? The updated mapping solution looks like we cannot do that anymore so that would be a change.
Is the status column indicative of whether it's linked or not?
Can you demo the audit trail functionality please?
Is there an ability to add new buttons on tab level?
Only available in lightning?
Would like the designer to guide the user in the SFM creation.
The SFM creation interface should walk the user through the process of creating the SFM according to what the user is trying to achieve.
Can we highlight the colours and sections on the Child Section tabs with different colors?
Could the save button auto-save all components?
I'd love to see api name here as well. we have some fields with the same names.
Oh…there is create new button option?
Instead having only save defined in old way?
Can we show errors of validations directly while entering the value instead of save button now?
When we can see this?
If you missed the session, here's the Video Link : 1549 and the Design Time: Designer 2.0 Presentation! I look forward to your responses, and our next Design Time together.
David Brieck Sharath Satheesh Michael Majerus Sonia Genesse Ramesh Kotamareddy Richard Lewis Esther Fournier I know some of these questions were yours! Please take a look and let me know if you have any feedback.
Doesn’t compatible with different Data Types - it takes only related text to text or number to number
- Need further clarification.
I don't know if this was mine, but when you're trying to map fields, it will only let you map fields if they are the exact same type. It would use useful to be able to map numeric fields to text fields, date to text, lookup to text, etc.
Hello Anita D'Souza. Thank you for posting this. For us the most important items are the: fields not needing to be on the layout, the API names appearing on the designer, and the ability to have a 'NULL' function which can be used in SFM Mapping upon SFM load. I think the first 2 items are being addressed, the third item is a nice-to-have. We are currently achieving this same result using an SFM formula, but an SFM Literal would be even better.
One item which is greatly impacting our use of the current designer is the 'Shockwave' error which prevents loading of the designer, or hangs during load. This just started to affect us in a big way about 1 - 2 months ago, so I think it might be Google Chrome version related, but I'm not sure if we have another option as Chrome is the recommended browser for SMax. Any ideas you have about that issue would be welcomed. On average it takes ~5x longer to work in the designer than it did a few months ago.
sfm designer sfm transaction designer null null field sfm sfm literal sfm literals
Hi Michael- I am checking on value map to null with the team and will get back. Regarding 'Shockwave' error, this is due to the current designer being on Flash. Have tried these steps: https://www.dell.com/support/article/us/en/04/sln186210/how-to-fix-shockwave-flash-crashes-in-google...
Hi Michael - For new records if the field is not mapped then it would be considered as blank/ empty /Null. Here the ask is to have an option to clear the value of the existing record through field mapping - correct.
Thanks Michael. Will get back to you on this.
Will there be a ‘Where Used’ for expressions so we can see where or if an expressive is in use before we decide if we need a new one or can safely modify an existing one?
Yes Mark Taylor - The plan is to have similar 'Where Used' modal on every reusable SFM component to provide information on where it is being used.
Thanks. Just watched the video of the call and see my point is well covered. Should have done that first!
Btw - the video stopped with just under 9 minutes to go so didn’t get that last bit. Anyone else reported this?