attachment mandatory requirement

[SD_Chandan]

The requirement is to ensure that when attachments are copied from another record, they do not satisfy the mandatory attachment requirement. Users must upload at least one new attachment on the current record and should not be allowed to proceed with only the copied attachments.

[SD_Chandan]

@Tanushree Maiti  Thanks for your solution and response.

[Gilbert35]

I think that requirement makes sense. If copied attachments are allowed to satisfy the mandatory attachment rule, it defeats the purpose of ensuring that each new record has its own supporting documentation. Requiring at least one newly uploaded attachment helps maintain data integrity, improves traceability, and reduces the risk of users relying on outdated or irrelevant files.

One approach could be to distinguish copied attachments from newly uploaded ones with a flag or timestamp. The system can still display copied attachments for reference, but validation should only pass once at least one new attachment has been uploaded for the current record. That keeps the process flexible while ensuring every record has current documentation.

I work with a local service business, and we've found that keeping each job's records separate instead of relying on copied files makes audits and customer follow-ups much more reliable. The same principle seems to apply here.

[SD_Chandan]

@Gilbert35 
Thanks for your solution and response.