Teamspace integration with Portfolio Planning Workspace

[Amritha1]

Hello All,

I've installed Teamspace1 plugin and I'm seeking advice on how do we integrate TeamSpace and Portfolio planning Workspace. The below link has been kept as a reference yet I would like to know how to proceed with this further.  The documentation suggest to :

1. Create one alignment integration for all the team spaces. On the alignment side, create extended tables to store individual TeamSpace table data (like TSP1 Portfolio [sn_align_core_tsp1_portfolio], TSP1 Demand [sn_align_core_tsp1_demand], TSP2 Project [sn_align_core_tsp2_project], and so on).
2. In the alignment integration, map the extended tables you have created in Step 1, to the respective TeamSpace tables (like tsp1_portfolio, tsp1_demand, tsp2_project, and so on)

My question here would be, which table should we extend while creating table to store individual TeamSpace table data. i.e  TSP1 Project [sn_align_core_tsp1_project] should be extending sn_align_core_project or Planning Item? 

Requesting help with the step-by-step procedure .

Working with Teamspaces (servicenow.com)

Any advice and/or feedback is highly appreciated.! Thanks

[Prashant_S]

Please extend sn_align_core_project while creating sn_align_core_tsp1_project. 

[phil bool]

You might not need to do that - why not just use the Execution Table field to separate the Teamspace1 Project/Demand records from records in your other tables?

[Amritha1]

Hello @Prashant_S !

Thanks for the response.

The sn_align_core_project table is not extensible by default OOB configuration. Would you advice to make changes to that? I've tried the the below process 

1. Create sn_align_core_project table (Application: Portfolio Planning Core) extending the Project sn_align_core_project table. The sn_align_core_project table was not extensible by default, hence made necessary config changes for that table.

2. Navigate to Portfolio Planning- > Integrations-> ServiceNow Internal

3. Create a Table map

4. Create corresponding field maps.

5. Cick "import"

Import was not successful due to the below error

 I also tried creating the sn_align_core_tsp1_project table extending the sn_align_core_planning_item table. In this case, I was not able to choose the field maps between alignment and execution table. Seems like the sn_align_tsp1_project doesn't have all the relevant fields of tsp1_project. But with the minimum possible field mapping , the import was successful though.  If I proceed with this method, should I create all the necessary fields within the sn_align_core_tsp1_project table manually?

Any feedback is highly appreciated.

Thanks,

Amritha

[Prashant_S]

Hi Amritha,

Yea sn_align_core_project is not extensible and you need to make it extensible at dictionary level in order to extend it. However, I would recommend to follow the second approach where you extend sn_align_core_planning_item table and create the project specific columns manually in your sn_align_core_tsp1_project. 

Please mark my answer helpful if it solves your problem. 

Thanks,
Prashant