Provisioning Engine: ListId token does not contain the id of a created list when the rootsite contains a list with the same title
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 259
- Forks
- 161
- Avg merge
- 10h 33m
- Merged PRs (30d)
- 1
Description
Sort of re-opening this issue. Encountered this today.
I have a provisioning template with a {listid:MyList} token which often results in a wrong GUID.
Basically, within the same template, I am creating multiple lists with some fields.
- List A with a date/time field X
- List B with a lookup field Y pointing to field X in list A
When creating multiple subsites using this templates, the result of {listid:ListA} always returns the same value.
In List B:
<Field Type="Lookup" Name="y" DisplayName="Y" ID="{guid}" Required="TRUE" EnforceUniqueValues="FALSE" List="{listid:ListA}" ShowField="x" />
Am I missing something or is this still broken?
Thanks in advance for any help!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the provisioning engine's {listid:ListA} token resolution and the XML lookup field shown in the report. Reproduce a template that creates List A and List B across multiple subsites, then verify whether each generated lookup uses the GUID of the newly created List A rather than a repeated value.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100