![]() ![]() The “Document Attachment Details” page is where the magic happens. ![]() The “Attachments” action has the following OnAction trigger code: trigger OnAction()ĭocumentAttachmentDetails: Page "Document Attachment Details" ĭocumentAttachmentDetails.OpenForRecRef(RecRef) Let’s take a look at the Customer Card page in standard BC. Let’s first look at how standard document attachments work. If you want to add another table, whether a custom table or another standard table, you will need to subscribe to some events to make that work. Standard BC has a limited number of tables that have document attachment capabilities. The more complex compound PK works the same, you just need to set more fields. I’ll focus on single field PK records in this post, so tables where a single Code20 field has the unique identifier of the record. Take a look at the Document Attachment table (table number 1173 in the base app) for the field definitions. The reason why it’s not so simple is because the Document Attachment works with RecRef instead of a hardcoded table relationship. It took some time to figure out how it actually works, and this post explains the whole thing, including how to get document attachments through the posting process. When my client said they see all attachments for all records, I realized it is a little more involved. Thinking this was a quick and easy one I added the factbox, set the link, and went on with my day. One of my clients had asked me to add Document Attachments to Bank Deposits. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |