Use Copy Master Detail Record and Data Validation
Hi, I'm using the Copy Master Details button. I'm stuck on how to get this functionality: 1. User clicks button 2. User goes to new record 3. If the user tries to save the new record without changing the text field that is used in the Copy button, a data validation rule would prevent them from saving. I can't do this because I can't have a unique field and have the copy master detail button work. I thought there was a work around with the custom table rules but can't figure it out. How can I use Copy Master Detail wizardand prevent the user from saving the new record with the same name as the copied record? Thanks community. ------------------------------ Raymond Sakar ------------------------------
Search related fields for Duplicate
I have a related field that has a dropdown where you can search as typical (probably 30,000 records) for a particularly entry number (number is really an alpha numeric code). If the record the user wants does not exist, I have a text field that says 'Enter New Entry Number'. However, if they manually enter a new entry number that already exists (perhaps they didn't search correctly or even try to search), I want the system to not allow it. I eventually use one of their two choices in an automation. So alternately, is there a way in an automation to say "If exists, do x y z. If does not exist, add record, then do x y z" Is this possible? ------------------------------ Mike Tamoush ------------------------------
Enforce my Opportunity Totals to match my order totals
I have a project management app that has a CRM aspect to it as well as order management. The structure for my following question is Projects < Opportunities < Orders <Invoices. During the sales cycle there are no related orders or invoices. There is an opportunity with a field in it called value to track the revenue for the opportunity. Won the user hits the Win button it fires off an automation to create tasks to various users and one of them is to the Project Coordinator on the project to enter the order in Quick Base. Another one is for the Project Coordinator to build out the invoicing schedule in Quick Base. Now what I have noticed is my team is often hitting that win button before updating the opportunity with any final pricing modifications in place so the total of orders does not always match the opportunities. I want to enforce this to prevent that from happening. However, currently I do have it set where each opportunity could more than one order (sometimes there are various phases). Long Story short the total of the invoices must add up to the order. Total of the orders must add up to the opportunity value. I need to keep that all in sync. So thoughts on best ways to enforce this data? I did place a data validation on the opportunities table that says If([Cumulative Total Sell] != Value, "The opportunity does not match the total of your orders. Please update the opportunity value."). I have a check on this to see if the phase of the opportunity is won so it doesnt run on non won opportunities So that should catch the opportunities table if they save something on there. However, how do I enforce the orders and invoices tables? Or I guess holistically how do I ensure those numbers maintain as a match throughout the process as the project develops? Only other option I can think of is removing the sell value from the order table and have it as a lookup from opportunities but I really did not want to do that. ------------------------------ Ivan Weiss ------------------------------Exception for Data Validation Rule
I'm working between two tables: Jobs and Price Increases. One job can have many price increases. I'm using a data validation rule to not allow a Price Increase to be added if the value in the Increase Effective Date matches a summary field that looks at the parent Job and pulls in the Maximum Increase Effective Date (one job should not have more than one price increase scheduled for one day). This works great when adding new records. But if I try to edit and then save the Price Increase record that has the Maximum Increase Effective Date, I get my data validation error (As I should, the two date fields match). Any ideas of how can I set an exception to the data validation rule? This is the rule: If([Rate Effective Date]=[Service - Maximum Effective Date], "error message". Thanks! ------------------------------ Heather ------------------------------