Forums

Is there a OOTB solution to prevent a record blank get created Cancel The title field is required!

1. Missing user

   
   06 Sep 2023

   Link to this post

   Hello there
   
   Basically, I have a multiple entity, and there is a relationship between them. There is a scenario that I will hide the fields from the other entity, but the record is getting created empty.
   
   Is there a way to disable this second entity?
   
   Best regards,
   Madson Almeida
2. Missing user

   
   08 Sep 2023 in reply to Missing user

   Link to this post

   Hello Madson,
   
   There may be a way to do this by utilizing the Rule Manager, but I would need some additional information.
   
   Essentially, you have a form that is tied to two different entities, is that correct?
   
   Is this part of a Form Flow? 
   
   Are you trying to prevent the creation of dependent records based on certain logic from the primary entity, is that correct as well?
   
   Once I understand the current structure, we should be able to figure out a definite solution for you.
   
   Thank you,
   
   Dustyn 
3. Missing user

   
   22 Feb 2024

   Link to this post

   I have something similar and wanted better to understand. When you create a form for a page and have a submit button does that create a record in CRM on submission (I am assuming so)? 
   
   We had a form flow created where there's an introduction page/product selector page as page one, the submit is set and then tt creates a blank record in CRM as the form is "submitted".
   
   With this in mind should the first page or product selection be passed through as a variable to another page? And have the submission on that second page? What's the best way to pass selections on the first page to another page.
   
   
   
   
4. Missing user

   
   29 Feb 2024 in reply to Missing user

   Link to this post

   Hello Edson,
   
   Yes, even with a form flow, whenever a record is progressing forward, and the query string is being developed a record is being created even though the "Submit" function on the form is not visible. 
   
   In these scenarios clients usually produce a status on the entity record that the form is generating to indicate if a portal form is pending. 
   
   As for how products and/or any other entity records move through the process, this would be completely dependent on how you build out the relationships. For instance, if you are creating an Order for a Customer record and that Order needs Products selected, the relationships between these entities would just need to be set correctly. 
   
   Whenever looking at a form, Default usually means that whatever record is being created is a new record. Any related records will have to have their relationships built out if not out of the box.
   
   Please let me know if there are any other specifics. We have an option to create a support ticket as well if needed.
   
   Thank you,
   
   Dustyn