Can I have a job automatically duplicate itself when a certain condition is met?

  • 0
  • 1
  • Question
  • Updated 4 years ago
  • Answered

I have an estimating table that lists when bids are placed and accepted. I also have a summary report which shows how many bids were placed and how many were accepted on a monthly basis. The summary report is based off of the field [bid date] which is a formula date field that changes depending on whether the bid is accepted or not. It needs to change because if a bid was sent in January but accepted in February then the information for when the bid was accepted needs to reflect on the summary report for February. The issue is that I still need the information for when the bid was placed to reflect on the report for January. Is there a way to have the bid duplicate itself when it is accepted so that there is still a job with information when the bid was placed as well as a job with information as to when it was accepted? For instance, is there a formula that I can have for a checkbox that will duplicate the job when its checked?

Photo of Brandon

Brandon

  • 120 Points 100 badge 2x thumb

Posted 4 years ago

  • 0
  • 1
Photo of Harrison Hersch (MCF)

Harrison Hersch (MCF), Champion

  • 40 Points
In general, best database practice would be to only store the information once. In this case, it is probably not necessary to have the same record twice (this introduces some challenges such as managing the accuracy of the information across recordĀ copies).

You could probably achieve a similar result by simply storing different date values either in fields or, more preferably, as a new level of hierarchy. So in many scenarios, we have complex status mechanisms that account for things like this. Here is a scenario for a high-end retail sales application we have built:

  1. Customer is quoted for product on Jun 1.
  2. Customer revises quote on Jun 15.
    1. "Quote Date" now reflects as Jun 15. This was a specific business choice.
  3. Customer leaves deposit July 1 amounting to 25% of total value. This is automatically flagged as a deposit.
  4. July 5, customer deposits another 60% (now totaling 85%). Because it exceeds 75% (specific business rule), the inventory is now automatically reserved, BOM is generated for the warehouse, and certain flags/statuses are updating.
All of these dates are reportable and are driving analytics. The process goes further down the line actually but the idea being it is all one instance of the record.

Does this help?
Photo of Brandon

Brandon

  • 120 Points 100 badge 2x thumb
I understand what you're saying and I know my question doesn't seem to make very much sense in terms of what would be more efficient. It really stems from how the managers want the layout to look. They would like to know if it is possible to have all of the information reported on a single summary report. In order to do this I need to be able to replicate a job so that the information isn't duplicated on the report. I partly wanted to know if it is possible to easily duplicate all the information for the summary, but I also just wanted to know if there was a formula that could do this for the future. If this is not possible then I will find a way to change the reports accordingly.