TeamDesk Knowledge Base & Support

Kirill Bondar  Staff  4/17/2019 4:44:30 AM

RecordSet denotes just the list of records. Suppose we translate <<RecordSet>> into table. But what columns to display there?
With master-detail relation we use columns from the view set up on a detail side. What could serve as a view for record set?

Pierre 4/17/2019 7:09:04 AM

Ideally:
any record should be accessible, be it on the view set up on the detail side or not.
It should be this way on the master-detail relation too (for the sake of the documents, I am including in the detail-side-view some fields which have no interest for the regular users of the database - this is not convenient)

More realistically maybe:
Before using TeamDesk, I had been using for 6 years an alternative solution (Q...).
In this solution, the subtables fields in documents were declared as a list : ex {1.12.13.14.23.34}.
The same might be used here.

Some examples of how I could use this.
Example 1)
I am sending a commercial offer to a customer (a Team Desk Document). This offer is about two types of articles (here : chemicals and transportation services).
This offer includes a first table with the list of the items, their quantity and price. At the bottom of the table I am displaying total l price...
In the same document, I then include a second table with detailed information about the first type of article (chemicals) and then a third table with detailed information about the second type of articles.
The three tables in the document are made of lines of the same teamdesk table.

Example 2)
I am sending a general offer to a customer.
I need a pdf document saying ' Dear Customer ... (personnalised), please find enclosed the list which would be suitable for you'. And then comes a table with the articles which match a couple of keywords I have written in my customer record.
Ex :
- Customer is Company
- Keyword is 'pigment'
- I need to list all the article of the 'Product' table including the name 'pigment'


Kind regards,

Pierre

Jorge Solá 6/8/2019 6:15:02 PM

I like this last idea, of being able to create on-the fly a matching condition to determine the subset of records to include in the document.

Jorge Solá 6/9/2019 9:50:04 AM

Come to think of it, this is already feasible:
1) Create a [Keyword] column, in the Customer table.
2) Create a lookup to this column in the Articles table.
3) Add a filter to the Articles view, something like:
If(not IsNull([Lookup Keyword]), Contains([Description], [Lookup Keyword]), true)
This way, only the articles containing the key word in their description will be listed & thus included in the document generated. If no keyword is included, the whole list is displayed.

Pierre 6/10/2019 7:07:37 AM

Hello Jorge

Thanks a lot for the idea - it is smart and it helps.

In order to make it work, one could:
- create a button with the following actions
1) change the 'Keyword' value to a specific value
2) Generated the document
3) change the 'Keyword' back to the original (normal) value

A bit cumbersome maybe, but I have no better option and it would work.

Kind regards,

Pierre

Jorge Solá 6/10/2019 9:47:02 AM

If you want to have the ability to specify several keywords (let's say 3), you could have 3 Formula-Text columns ([Keyword 1], ]Keyword 2], [Keyword 3]) that will respectively extract the 1st, the 2nd & the 3rd word in the [Keyword] column (through Left() & NotLeft() functions). Then change the above filter formula to something like:
If(not IsNull([Lookup Keyword]), Contains([Description], [Lookup Keyword 1]) or Contains([Description], [Lookup Keyword 2]) or Contains([Description], [Lookup Keyword 3]), true)