| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 6 months |
| seen | Nov 23 '12 at 22:32 | |
| stats | profile views | 1 |
|
Nov 23 |
asked | Can a workflow on one list update fields in a linked (joined) list? |
|
Nov 7 |
comment |
Joining two lists in a single view or edit form BTW I did some testing and the Title field does work in the connection (which helped me a lot to understand the problem, so thanks for that!) but as I suspected, a duplicate title causes multiple matches to turn up in the second list. See above for the solution, it needs to be a numeric ID connection, but NOT stored in a lookup column! |
|
Nov 7 |
answered | Joining two lists in a single view or edit form |
|
Nov 6 |
comment |
Joining two lists in a single view or edit form BTW I did consider using one list (and I may have to go back to that idea). Issues I forsaw were- 1) Column level permissions. Only Reviewers shoudl be able to edit Review fields. 2) Maybe i'm wrong but my understanding of content types is that each list row can only "be" one content type. So, if I create a row as a Request, I can't subsequently mutate it into a Review and work on the columns that would only exist in a Review. Have I misunderstood that? |
|
Nov 6 |
comment |
Joining two lists in a single view or edit form In theory there is no guarantee that Request titles will be unique, that's why I went for database-style ID lookups, they seemed safest (maybe I was naiive about SP oddities). The "additional fields" feature in SP2010 is pretty strange BTW, because it only offers you a small subset of the fields from the "other" (joined) list. If you could pull across all the fields from the Request as columns in Reviews I wouldn't need to try this procedure of joining lists on the page. |
|
Nov 6 |
comment |
Joining two lists in a single view or edit form BTW on the second point, as I understand it SP doesn't do column-level permissions, so this is effectively a way to work around that. |
|
Nov 6 |
comment |
Joining two lists in a single view or edit form Sounds interesting, but- 1) Seems weird that SP lists can't consume filter values from other SP lists? 2) "Actions" are new to me. Do I need to trigger a workflow to use them? If i'm looking at a single page in edit mode, I assume an action won't be triggered until the page is saved? 3) The required value (3 in this case) is only the 4th character if the Request ID is 1 character wide. In general list IDs can grow indefinitely, so I would need to use something like a regular expression to extract "All the digits up to but not including the first non-digit". Not sure if Sp can do this? |
|
Nov 6 |
comment |
Joining two lists in a single view or edit form I had a couple of reasons for using two lists- 1) Simplicity. When entering a Request the users see a simpler form, without any of the Review fields they don't need to see. 2) Permissions. Although I haven't got that far, the idea is that only Reviewers will be able to edit the Reviews list fields. (Note there's a question in my mind about the permissions of the workflow that creates the Reviews entry when a Request is created, but I haven't got that far yet). |
|
Nov 6 |
answered | Can i filter folders to show on different views |
|
Nov 6 |
awarded | Student |
|
Nov 5 |
asked | Joining two lists in a single view or edit form |