PowerApps : Move SharePoint custom list form to different site

Hello Friends,

I recently done some modification to SharePoint list form in PowerApps, I done all modifications and tested it as well. Everything was as per expected but now i was having requirement to move this form to another list in different site. I thought it is very straight forward requirement but to my surprise, i do not found direct option to export it. I seen this export option was there previously but now Microsoft have removed it. As SharePoint custom list forms are not listed in apps list hence we can’t use the default export option, so now how to export the SharePoint custom list form built using PowerApps to another site inside same tenant?

There are two ways using which we can export the list form.

I have created a sample SharePoint list, where list form is modified.

Main parent list holding just Title values.

Child list 1, holding reference using parent list ID column to Lookup_ID

Child list 2, holding reference using parent list ID column to Lookup_ID

I have modified the list form to just view values for current selected items and also using LookUp function matching value from list Child1PATest and Child2PATest list.

Option 1 –

1. Open the custom SharePoint list form.

Open SP List Form in PowerApps studio

2. Press Ctrl+Shift+S

3. Click on the “Save” Option from the left menu and click on “See all versions”.

Now you can see “Export package” option on the top.

Option 2 –

1. Go to List settings and click on ‘Form settings’

2. Select “See versions and usage” option

3. Now you can see “Export package” option on the top.

In upcoming post I will share how to migrate connections to different site. Sharing is caring.

Error while creating app catalog – Updates are currently disallowed on GET requests. To allow updates on a GET, set the ‘AllowUnsafeUpdates’ property on SPWeb

Hello friends,

Recently after creating a dev tenant, I proceeded to create tenant level app catalog site as I was setting up the SPFX environment. I selected ‘Create a new app catalog site’ and added needed details.

New App Catalog Creation

New App Catalog details

I got an error “Updates are currently disallowed on GET requests. To allow updates on a GET, set the ‘AllowUnsafeUpdates’ property on SPWeb” when i tried to create a new catalog site.

New App Catalog Error

After scratching head and after some googling, i found out that we need at least one site collection created other than the default site gets created with tenant. Then only new app catalog creation will work.

New Sample Site Creation

So, i have created a Test site and tried again to create new app catalog and voilà, it worked.

Looking like Microsoft should improve on error handling.

Sharing is caring.

SharePoint online: Error ‘Updates are currently disallowed on GET requests. To allow updates on a GET, set the ‘AllowUnsafeUpdates’ property on SPWeb’ while creating new app catalog site

Recently I have created new E5 personal tenant for my development and testing purpose. I wanted to deploy and test the SPFx component in that tenant, hence I tried to create the App catalog.

I directly went to SharePoint admin center in Office 365 and tried to create new App catalog site, like following.

App catalog Creation

I got the error ‘Updates are currently disallowed on GET requests. To allow updates on a GET, set the ‘AllowUnsafeUpdates’ property on SPWeb’.

App catalog Creation Error

I initially thought that the error is due to some technical glitch and no clear reason of the error explained in error and hence I tried to create App catalog site couple of times more but no luck and got the same error.

The solution is bit weird as I just created new tenant, I do not have any site created yet and I jumped directly to create app catalog site.

Then I have created one test site in tenant.

One Site Created

And it worked, I again tried creating the App catalog site and it worked.

App Catalog Success

So we need to at least create one site before creating App catalog. The only concern is Microsoft should provide some meaningful error message so that we will not be confused.

Sharing is caring, stay safe. Take care.

SharePoint online and on premise: Event receiver (receiver job) for Managed metadata service

Hi Friends,

Recently I came across a requirement where I need the deleted event receiver on managed metadata service. I initially thought there may be definitely some direct solution exist for this kind of requirement but unfortunately no synchronous event receiver available which trigger immediately after term got deleted from termset.

After some research I came across a method ‘GetChanges’ which is available at TermStore and TermSet both.

This solution worked well and I have created a PowerShell script which checks TermStore for any deleted terms after specific interval which is configured in task schedular.

What a wanted to achieve is to set the term ‘Uncategorized’ to the list item whose original term got deleted.

Method documentation at TermSet.GetChanges Method

Solution for SharePoint 2013:

$dt = Get-Date;
$dt = $dt.AddDays(-1);
$url = $webAppURL;
$tax = Get-SPTaxonomySession -Site $url;
$termStore = $tax.TermStores[0];
$deletedTerms = $termStore.GetChanges($dt, [Microsoft.SharePoint.Taxonomy.ChangedItemType]::Term,[Microsoft.SharePoint.Taxonomy.ChangedOperationType]::Delete);

In above example I was looking for deleted term in previous number of days (past 1 day in above example).

There are four overloads available for GetChanges method, the one I used have following parameters –

startTime of type DateTime (A UTC time indicating the earliest change to be included in the result collection)

itemType of type ChangedItemType (Indicates the type of ChangedItem objects to return) Following are the possible values of Enum.

Changed Item Enum values

operationType of type ChangedOperationType (Indicates the types of operations to return)

Following are the possible values of Enum.

Operation Type Enum values

Method GetChanges returns us collection of ChangedItem objects that represent changes to this TermStore since a specified time, restricted by item type and operation type.

End to end approach –

1. Find which term got deleted using GetChanges method we will use the term IDs we get in next step.
2. Fire a SPQuery to get the items associated items from taxonomy hidden list.
3. The items found in step 2 can be used to find actual list item using relation between taxonomy hidden list and actual list.
4. We can update ‘Uncategorized’ term in the respective list item.

Office 365/ SharePoint online :

This method will work same way for Sharepoint online as well –

    static void Main(string[] args)
    {
            AuthenticationManager authenticationManager = new AuthenticationManager();
            ClientContext clientContext = authenticationManager.GetAzureADCredentialsContext("My tenant URL", "email", "pwd");

            TaxonomySession taxonomySession = TaxonomySession.GetTaxonomySession(clientContext);
            TermStore termStore = taxonomySession.GetDefaultSiteCollectionTermStore();
            ChangeInformation changeInfoObj = new ChangeInformation(clientContext);
            changeInfoObj.ItemType = ChangedItemType.Term;
            changeInfoObj.StartTime = DateTime.Now.AddDays(-20);
            changeInfoObj.OperationType = ChangedOperationType.Add;
            ChangedItemCollection changedTerms = termStore.GetChanges(changeInfoObj);
            clientContext.Load(changedTerms);
            clientContext.ExecuteQuery();

            if(changedTerms != null)
            {
                foreach(ChangedItem oneChangedTerm in changedTerms)
                {
                    Console.WriteLine(oneChangedTerm.Id);
                }
            }

            Console.ReadLine();
     }

You can run above code in a task scheduled EXE, PowerShell script or a Azure Job also work. Also you can decide the frequency according to your requirement, in my case I was running this daily once.

Hope this will help. Happy coding.

SharePoint online: Creating managed metadata column using site script and site design

Hi Friends,

Recently I came across a requirement to create managed metadata column through site script which should be available after creating the site.

I tried different approaches and tried to find many alternatives but no fruitful information found after tried multiple column schema xml I got it working.

Will start with showing the term store.

Figure 1: Office 365 – Term store

I have created a sample group ‘Test Group’ and underneath it a term set named as ‘Business Area’ with some sample terms.

Managed metadata column in SharePoint online works same as on premise one. There are actually two columns in the list one column is with of type ‘TaxonomyFieldType’ and other column is created with the with format fieldnameTaxHTField0 of type Note.

The Taxonomy column holds Term name and a lookup with the TaxonomyHiddenList. TaxonomyHiddenList can be found at /Lists/TaxonomyHiddenList/AllItems.aspx this list will hold the details of the terms that are used in any managed metadata column.

Hence for creating managed metadata column through site design we need to create two columns, one of type Note which we need to use while creating actual managed metadata column.

We need multiple GUIDs while creating the metadata column,you need to replace values from your tenant,  as follows –

1. SspId Taxonomy term store guid
2. GroupId Taxonomy term set group guid
3. TermSetId Taxonomy term set guid
4. TextField Note column guid

Following is the site design JSON file. This include both the columns.( Save content in .json file)

schema_json

I have created the site design using ‘SharePoint online management shell’

Figure 2: Office 365 – Setting site script and design through PowerShell

Let’s try now creating new site using the newly created site design.

Figure 3: Office 365 –Create new site with new site design

Looking like we got success with creating new columns.

Figure 4: Office 365 – Success status shown

Let’s add ‘Business Area’ column in document library to test if the column is working or not.

Figure 5: Office 365 – Add column to document library

Let’s try uploading new document in library and check if the column is showing the values form term set.

Figure 6: Office 365 – Terms are displayed for option in column

The column provisioned through the site design is working as expected.

Let’s check the TaxonomyHiddenList now.

Figure 7: Office 365 – Taxonomy Hidden List

And if we check by editing item properties you can see same GUIDs we added in JSON file.

Figure 8: Office 365 – Term store, term set and term ID visible TaxonomyHiddenList

Considering 30 verbs limitation (as on date) per site design, this may not be a good solution to spend two verbs for a single managed metadata column.

The purpose of this article is to save some time if anyone have same kind of requirement.

Sharing is caring.

SharePoint online / SharePoint 2013: Sharing variable values between search control and display templates

Recently I came across to a scenario where I need to set the variable in control template and the value of the variable should be accessible in item template and vice versa.
I was showing some data in item templates and using third party pagination for displaying the search result, needed the value of pagination size which is available in control template.
I tried with normal JavaScript variable but due to the scoping in display template it was not available for me inside the item template.
Solution 1:
We can use Windows.variable which is nothing but global variable creation on the scope of the window object and hence will be accessible throughout the scope of windows object.
Control Template:

<!--#_ window.PageSize = "30"; _#-->

Item Template:

<!--#_ alert(window.PageSize); _#-->

Solution 2:
Another better alternative is to use the built-in ctx object which is already shared between the control and item display template.
Control Template:

<!--#_ ctx.PageSize = "30"; _#-->

Item Template:

<!--#_ alert(ctx.PageSize); _#-->

Happy learning.