ContributionsMost RecentMost LikesSolutionsRe: Formula to append field value into a different field that also allows user entry? True, I could hide it in view mode, but most of the time when a record is open, users are editing, so its not an issue. But thanks for the tip! ------------------------------ Diane Sinawi ------------------------------ Re: Formula to append field value into a different field that also allows user entry? Thank you, it worked great!! I didn't think of creating a new field to hold both pieces, but I don't mind having 2 name fields, as the users won't care, and it gets us what we need, and we can adjust our reports to use the new field only. Thank you again!!! :) ------------------------------ Diane Sinawi ------------------------------ Formula to append field value into a different field that also allows user entry? Is there a way to append a value from field A into field B that is a user entry field, while allowing user to also manually enter a value in field B? We have a form to upload Documents that also captures information from another table (Task table). The process is that we create a Task record which includes a section to upload a Document - the Add Document link in the Task record opens a new Document record, and info from the Task autopopulates into the Document record. One of the Task fields that autopopulates in the Document record is "Evidence Number" - (eg: 12A, 07B, 34D). In the Document record, users create a name for the record in the field "Document Record Name" (eg: Server Log, New Hire Population) We need the Evidence Number value listed in the Document Record Name and currently ask users to manually enter it. But its often left out, so we'd like the Evidence Number to autopopulate into Document Record Name, but still allow user to add their own "name". EXAMPLE: if Evidence Number is 12A, then Document Record Name would autopopulate with "12A" or "12A -"but still allow user to enter values. After user enters "Server Log", the field value will appear as "12A Server Log" or "12A - Server Log". Is this possible if we make Document Record Name a formula field? If so, what would be the formula? Also, would there be any issues with reports showing both values in the field? Thank you for your help! ------------------------------ Diane Sinawi ------------------------------ Re: Issues with form rules and notifications when Log Edits is enabledI ended up finding a simpler solution, as I have limited experience with formulas. I removed logging from Review and Approval field. I added 2 new fields: Approved By and Approved Date. They autopopulate with current user and date when value in Review and Approval field is changed to "Reviewed and Approved". They are read-only fields, so the users cannot populate those fields themselves. Also, I made the Review and Approval field not editable when it is changed to "Reviewed and Approved". If someone accidentally approves, if they don't save they can just close the record and it will remove the value and make the field editable. If they save, we can temporarily suspend the rule, remove the value, then put the rule back. This gets me the ultimate result I need - ability to log who actually approved and date in some way, and ability to keep approvals from being edited. There's no conflicts with notifications. But I really appreciate the time you took to help. ------------------------------ Diane Sinawi ------------------------------ Re: Issues with form rules and notifications when Log Edits is enabledI ended up finding a simpler solution, as I have limited experience with formulas. I removed logging from Review and Approval field. I added 2 new fields: Approved By and Approved Date. They autopopulate with current user and date when value in Review and Approval field is changed to "Reviewed and Approved". They are read-only fields, so the users cannot populate those fields themselves. Also, I made the Review and Approval field not editable when it is changed to "Reviewed and Approved". If someone accidentally approves, if they don't save they can just close the record and it will remove the value and make the field editable. If they save, we can temporarily suspend the rule, remove the value, then put the rule back. This gets me the ultimate result I need - ability to log who actually approved and date in some way, and ability to keep approvals from being edited. There's no conflicts with notifications. But I really appreciate the time you took to help. ------------------------------ Diane Sinawi ------------------------------ Re: Issues with form rules and notifications when Log Edits is enabledThank you Mike. I'm considering your and Mark's advise both. I'll update after I try something out. ------------------------------ Diane Sinawi ------------------------------ Re: Issues with form rules and notifications when Log Edits is enabledThank you Mark. I'm considering your and Mike's advise both. I'll update after I try something out. ------------------------------ Diane Sinawi ------------------------------ Issues with form rules and notifications when Log Edits is enabledI have a multiple choice field (Purchasing Review and Approval) with one value "Reviewed and Approved." The field is empty until someone approves. To log the user and date, I enabled Log Entries for this field. After value "Reviewed and Approved" is selected, I don't want this field to be editable. However, my form rule is not working in this field. If I select a different multiple choice field that does not have Log Entries enabled, the rule is working. NOTE: originally I had 2 values "Not Reviewed or Approved" and "Reviewed and Approved", but it had the same issue. Also, I've set a notification (currently to myself for testing) that when the value changes to "Reviewed and Approved", a notification is sent. This is also not working. Is this a QB limitation when using Log Entries, or am I doing something wrong? Thank you for your help! ------------------------------ Diane Sinawi ------------------------------