Transcript:
0:00 [Music]
0:05 in this video we're going to look at how
0:08 we can use the North52 data package to
0:11 import dynamics portal configuration
0:14 data the scenario we have is that we've
0:17 got a product registrations entity and
0:20 we want users to be able to complete a
0:22 product registration form on our portal
0:25 we have a managed solution to import all
0:28 the components required for this
0:30 including the data package so we're
0:33 going to import that managed solution
0:38 this could be downloaded from the North
0:41 52 support website once that the
0:44 solution has been imported
0:46 we need to publish all customizations
0:48 the solution itself actually contains a
0:52 new entity called product registration a
0:55 web form and a web view and then a
0:59 real-time workflow inside there to
1:02 update the product registration name as
1:03 it is created so it has imported
1:06 successfully we just need to do a
1:08 publish all to unpack the data package
1:11 in the system and that will be available
1:14 for us to use shortly once the public
1:19 public gene customization step is
1:22 finished we can go to the system jobs
1:26 and check to see that the North52
1:30 publish all workflow has been completed
1:35 so we know a gate from settings to
1:39 system jobs we can see that the North52
1:44 publish all is in progress and we just
1:47 wait for that to complete once that has
1:49 completed we can then navigate to our
1:52 data package and we can see that we have
1:59 got a data package here called product
2:01 registrations
2:03 and we open that data package up and we
2:08 can review its contents here first step
2:11 in our data packages that we might want
2:14 to deactivate some plugins and processes
2:16 this is particularly useful for web
2:19 portals where you want to disable any
2:21 plugins that are on the web page create
2:25 because the process of the creating web
2:29 page creates a duplicate child page
2:31 whereas we won't don't want to do that
2:33 because we're going to be creating that
2:34 as part of the data package itself we
2:38 need to create some entity permissions
2:41 we need to associate those two web roles
2:44 many depending association to web roles
2:46 we need to create an entity form we need
2:49 to create some entity form metadata an
2:52 entity list of the web pages itself to
2:57 hold the the web forms and the web lists
3:00 some updates post web web page creation
3:05 to update the self referencing fields so
3:09 the parent page in the web page for
3:10 example we also need to do some updates
3:14 post web page creation to link the list
3:18 ID to the web page we need to create a
3:22 web link of the navigation and then
3:25 finally we need to activate any plugins
3:29 or processes the product and plugins and
3:32 processes that are activated deactivated
3:35 are defined in our configuration so if
3:39 we come and see here so the entities to
3:41 disable we can see here that we've got a
3:43 number of a TX entities that we've
3:46 decided we want to disable for this
3:48 particular data package and these will
3:51 get disabled and re-enabled on execution
3:56 of the data package if we come across to
3:59 our portal we can see here that we
4:05 haven't gotten anything in our support
4:06 menu this is where we're going to add
4:08 our new functionality so if we come back
4:11 to the data package what we need to do
4:14 is simply come across to our
4:16 execute fly out here and click the
4:20 execute button itself and once this is
4:23 executed all the necessary components
4:25 would have been deployed for us to
4:29 utilize this functionality on our on our
4:31 portal I can see that there was a
4:34 success there were no errors so all we
4:37 need to do now is come across to our
4:39 community portal here and go to the
4:44 services about page clear the cache once
4:49 that's done if we go back to our main
4:51 website we should be able to see the
4:55 changes in our menu and we can see here
4:59 now that we have got menu here called
5:02 product registrations and the ability to
5:07 add a new product registration some
5:14 products in here and they don't see any
5:16 number that we want to put in here click
5:18 Submit and then we can see we go back to
5:22 our project product registrations page
5:24 that record has been created in here so
5:29 that's how simple it is to execute a
5:32 data package and deploy changes out to a
5:35 portal for further information please
5:37 see our website North52 comm or our
5:40 knowledgebase at support North52 comm