Not sure if what I’m trying to do is possible but would appreciate any advice.
I have a form with three tables for work history:
Company1, Start Dt1, End Dt1
Company2, Start Dt2, End Dt2
Company3, Start Dt3, End Dt3
My goal is to have a view of previous companies (categorized) showing the start and end dates in columns 2-3. The first column is easy (@Trim(Comp1:Comp2:Comp3), but I can’t figure out how to match up the dates with the companies in columns two and three.
I could add all three values to the first column, but this would stop me from categorizing by company effectively.
Subject: One Last Thought - first column is an individual?
Start with the view column for the person’s name, second column start date (ascending), end date (ascending), THEN the company name. That way it should categorize on the person, THEN their job history … at least at this time of the afternoon without testing that is my inclination
Well, at any rate, good luck. Sounds like a very tough one. Cathy
Subject: RE: One Last Thought - first column is an individual?
My goal is to get a view where you can click on a company name and see everyone who’s worked at that company in the past and when they worked there.
So the first column would be categorized containing Comp1:Comp2:Comp3, etc., and then the second and third columns would show the corresponding dates for when the person was at that company.
Since I don’t think that can be done, I guess the best way to do this is to build a hidden field on the form and put in a formula like this…
My only problem with this is I can’t get the company categories to collapse, so I have a new main category for that company based on each year someone started.
Subject: RE: One Last Thought - first column is an individual?
I don’t suppose you’re interested in making it a report created on demand and displayed in a rich text field? You could prompt for the company first and then create a report showing just the entries for that company.
with multivalue fields? There is a lot on this forum about creating a table and adding rows, which correspond to the multi-values of the fields … hth Cathy
Subject: Multiple corresponding fields into multiple columns
Thanks for the suggestion but we have too much data for multi-value fields. In addition to start and end dates, I’m putting in fields for job description, title, etc.
The only fields I want in the views are the start and end dates.
in the view you want to show only the company (which could actually be 10 instead of 3??? if like a resume), start and end dates? And for each entry, you will also have a description and title? Or are those single value fields? that would help with getting how to set up the form (table) and the view sorting properly …
Subject: RE: Would this correspond to a resume then?
Yes, similar to a resume but not quite as detailed…though the job description field could contain a lot of data. Also, other fields (reported to, city, state, department).
Hi, Mike - do you in fact mean one table with three columns, first company, second start date, third end date? Because if that is what you are looking for, there is a way to create a table with multi-value fields and to add the number of rows necessary to accommodate. If one of the three fields were left blank, to make sure they lined up in the view you would have that field fill with a placeholder like a hyphen. But if you have a great many fields that will repeat almost all of the information, it might be better to have a lot of separate fields (comp1, comp2, comp3, as you first mentioned) and then hide the fields that end up being null. Then I would go back to your original scenario of concatenating the fields, though, as you said, the company names would not sort correctly. Hope you get some better ideas elsewhere! Will stay posted,though. Good luck! Cathy
Subject: RE: Noticed you said 3 tables - why not one?
Cathy,The multi-value field idea will not work. My plan is to build several tables containing all work info for each job (company, dates, location, title, job description, etc.) and hide the ones that aren’t needed.
Subject: Ah! Light bulb just went on - that makes more sense
I was thrown off by your mentioning only the three fields initially as being part of the the/a table (as being included in the view, but not necessarily part of the table layout). Hiding the unnecessary tables sounds like the way to go. Good luck, Mike! Cathy
Subject: Multiple corresponding fields into multiple columns
It’s quite impossible – while there seems to be multiple “instances” of a document in a categorized view, there’s really only the one. All of the results of a column formula will appear in the appropriate column, and it’s the view that splits up categories based on the multi-value in that column. If your column formulas “look leftward”, they see the multiple value, not the individual categories. If it were a web dealie, you could feed the data to the browser and let javascript write the user “view” to get row matching, but there’s nothing you can do in a Notes client application.
Subject: Hi, Stan, yes of course only one document
but if Michael wants things to “line up” only to the point of the first column (company), can he not sort by clicking on the column header and take it from there? When he opens the form, the lines should line up for begin and end dates, if that is all he is inputting into the table with the multi-value fields, and assuming, that if something is left blank, he has a hyphen or somesuch placeholder to keep things in line. As to whether all of these fields are multiple (like title, etc.), I am confused.
