search

pnp / PnP-Sites-Core

Microsoft 365 Dev PnP Core component (.NET) targeted for increasing developer productivity with CSOM based solutions.
Other
416 stars 643 forks source link

Calculated field creation fails #633

Open SuleymanA opened 8 years ago

SuleymanA commented 8 years ago

Which PnP repository to report the issue?

[x ] Bug [ ] Enhancement

Environment

[x] Office 365 / SharePoint Online [ ] SharePoint 2016 [ ] SharePoint 2013

Expected or Desired Behavior

I have created a site template using an existing site. I am trying to apply the template to a blank site collection rootweb. I have one calculated field with is basically just showing a choice field value, nothing more. Formula looks like this: =[{fieldtitle:MyField_x0020_name}]. Both sites have the same regional settings and language (English).

I expected the field to be created when applying the template

Observed Behavior

Receiving the following error: "The formula refers to a column that does not exist. Check the formula for spelling mistakes or change the non-existing column to an existing column.". Tried to move the referenced columns up in the template (it was initially below the calculated field) but the result is the same.

Steps to Reproduce

Thx for your help!

estruyf commented 8 years ago

This should be fixed in the latest DEV build. Had the same problem, but the PnP team (@erwinvanhunen) did an update to solve this issue.

Are you able to build the DEV branch code?

SuleymanA commented 8 years ago

Thx for your reply Elio! I haven't tried the DEV branch. I had to continue, facing deadlines, so just removed the calculated fields... I will give it a try next time. Faced similar problem few months ago with calculated fields, seems the chosen solution (tokenizing) is also not working. So a bit hesitant to put more time into trying again.

jansenbe commented 8 years ago

Problem is that fields added in the same template as the calculated field were not recognized by the token parser...we'll change this and add "added" fields to the token parser which will allow your scenario. Stay tuned for an update

Pieter-Veenstra commented 7 years ago

Is there any update on this? I've just started hitting this issue with some of my templates.

jansenbe commented 7 years ago

We support this scenario in our test automation: https://github.com/SharePoint/PnP-Sites-Core/blob/dev/Core/OfficeDevPnP.Core.Tests/Framework/Functional/Templates/field_add.xml#L60. Can you verify if this model is working for you as well?

Pieter-Veenstra commented 7 years ago

Hi @jansenbe,

In my case the calculated field is fld1 using fld 2 and fld3 in the calculation.

Within the xml fld1 is first listed therefore fld2 and fld3 don't exist yet when the template is applied to a new site.

jansenbe commented 7 years ago

Thanks for the additional feedback @Pieter-Veenstra. interesting problem as that would mean that we need to calculate the order in which fields are created...and one could cross reference so that no order would be fine. Alternative if skipping calc fields and applying them in a second round. Will mark as bug.

nilang-shah commented 4 years ago

I will appreciate any update on this issue! I am still facing the same issue!

nilang-shah commented 4 years ago

I will appreciate any update on this issue! I am still facing the same issue!

Recommendation made in #2081 resolved my issue!