I add custom profile in the package, however, I can't create the custom profile by installing. After more investigating, if I created the custom profile before the installation the package can update the fls and permissions. There is no way creating custom profile on installation? If so can I do that with installation script?
Took me a while to figure it out but here's the solution:
IN YOUR DE ORG:
Clone Standard Platform User profile (because is the one that has the Salesforce Platform license) and name it something meaningful like MyApp_Profile
Customize MyApp_Profile to match your desired access level for the users that will test or use your app
Add custom profile settings MyApp_Profile to the package
Go ahead an finish the package
IN THE TEST_ORG (OR YOUR_CUSTOMER_ORG):
Pre-create a profile by cloning the Standard Platform User profile and name it something meaningful like MyApp_TestProfile
Assign MyApp_TestProfile to a user
Install the package and on Step 2 (Choose security level) of the wizard you have to select the third option (Select security settings)
Under "Customize security" section make sure the MyApp_TestProfile (created on step 5) has the MyApp_Profile assigned (created on step 1)
Finish the Package installation
Log to the test or customer org with the user that has the MyApp_TestProfile assigned and choose your App from top right menu.
You're welcome!
I hope this solves your issue too!
Related
I'm doing a tutorial on communities, and after setting pages and themes, i wanted to add users. The access is made from the contact object.
I setup the community, but think i should have a link here
i setup the user of a contact like this:
User License = Customer Community
Profile = Customer Community User
Active = true
but when i try to log him in, i get: "Looks like this portal user is not a member"
I tried the same with another profile, a clone of the native Administrator profile, to which i added, in Profile Overview > App Permissions
Manage External Users = true
then, one by one, i activated all permissions, and still had that warning.
edit:
i'm using Classic
This is a developer licence
What am i missing?
The links disappeared because you killed off your own access to community (on Sysadmin, cloned profile etc). Do you remember editing this page? (sorry I had to censor some bits). If you removed System Administrator from the list of profiles - #fail.
If you can work with the new community and it's OK to have old one lying around - cool. If not - You might be able to resurrect it by exporting the community definition file, tweaking it and deploying back. I'm assuming you have some dev experience.
Prepare package.xml that contains
<types>
<members>*</members>
<name>Network</name>
</types>
Export the zip file (you don't neccessarily need developer tools, http://workbench.developerforce.com/ might be enough). Inspect the networks/YourCommunityName.network file. There should be a section similar to this
<networkMemberGroups>
<permissionSet>Censored1Access</permissionSet>
<permissionSet>Censored2Access</permissionSet>
<profile>Censored User</profile>
<profile>Admin</profile>
</networkMemberGroups>
Make sure "Admin" is on the list and deploy it back to org. It should give you access back and then you can add your customer community user's profile, permission set or whatever you plan to give them.
A month ago when https://my.knowledge.store/ was not existing I was able to edit the Cortana channel on dev.botframework.com, add new users to 'deploy to group' option and share the link with those users. Once user log in to their MSA and accept the skill they would be able to use the skill.
Recently, due to site changes Microsoft came up with new site called https://my.knowledge.store/workspace where Cortana channel and its publishing will be managed. I completely followed following link to deploy to group
https://help.knowledge.store/system_concepts/publishing/index.html#publish-to-group
but, I see few differences this time. It does not give
1. Link to share
2. Once deployed NEW users added are not tied to skill yet.
Is this a bug ?
'Publish to group' should be working. When you publish to group using the steps mentioned in the link, it will give you group access URL. This is the link you need to share for new users to test and use that skill.
You should be able to generate the link now. Please let us know if that is not hte case.
Picked up an existing project built on Composite C1 version 4.3, and I'm trying to install a package. All the information online says to go to System -> Packages -> Install Local Package, but I don't even see a Packages option on the System page at all.
I've tried to see if this option was disabled or not available in this version, but nothing definitive so far.
EDIT:
I do have direct access to code, so if there's a config file I could edit it directly, but haven't found anything that indicates where this might be.
It looks like the account that you are logging in with isn't the main admin account. It's probably a developer account to which the admin has added the ability to make backups and tweak Google Analytics settings. You'll need to contact the admin and ask them to give you full privileges, in order to install packages yourself.
If you have FTP access to the website, there is a way to move an account from one group to another:
Open: ~/App_Data/Composite/DataStores/Composite.Data.Types.IUser.xml
Find the user account for the user you want to change group membership for, and make a note of the Id GUID value.
Open: ~/App_Data/Composite/DataStores/Composite.Data.Types.IUserGroup.xml
Find the group you want that account to have membership of (ie: Administrator or Admin), and make a note of the Id GUID value.
Open: ~/App_Data/Composite/DataStores/Composite.Data.Types.IUserUserGroupRelation.xml
Make a backup copy of this file, just in case it doesn't work!
In the origional, find UserId GUID matching your account Id, then ammend the UserGroupId to the group Id. Save the file.
I've tried this out on my local copy of C1 and it appears to work. You should now have access to everything the admin has access to.
i downloaded the old version of C1 4.3 from github and started a new site, and looks like something is wrong with your site, because this version have package manager.
Something error on Log's Folder? (no Console Log item found in your capture)
I tested on this version (see the image uploaded), so, wich especific version have you?
The two files I needed to change were IUserActivePerspective, and IUserGroupActivePerspective. The perspectives for what I was missing were removed from the admin account, so I just needed to add them back there.
There is a current install of DNN on one of my local webservers - this was installed before I took over this position. I am trying to add a second site, but the instructions I am following appear to be for attaching an existing site. Do I simply run the installer to create a new site in addition to the current? I've never used DNN before, so I am going at this blind.
All information I am finding is referencing the same as the instructions link I provided. Any assistance is greatly appreciated.
To add a little bit more information, here is another area where I am confused. Referencing the link, it states #2 to add a binding to my site, then #3 is to add the new portal. What I am trying to do is create a new DNN site - one does not yet exist, so I cannot do step 2 until a new portal is created. As said, I've never used DNN. I was tasked today to have this done by July 4th (nice, huh) so today is the first I am looking at DNN ever.
What I have done is added a new portal and I assumed it would create a new bare-bones site for me, but that is not what happened (obviously). So, instead of just adding an existing site for DNN, how do I add a new one (that is why I asked if I needed to reinstall)? From what I understand, there was an initial website setup with the installation of DNN. That basic site served what they needed - I need to do the same thing again, but, as can be seen, I've no clue how to do so.
No, you don't run the installer again. Remember DotNetNuke is PORTAL Hosting software, meaning with just 1 install you can run ~unlimited websites (of course there's always limits, depending on the hardware you're running on).
For instance if you're DNN install is running on www.myweb.com, and you want to add a site for www.yourweb.com, you simply point your DNS entry for www.yourweb.com to the IP of your DNN install, should be the same IP as www.myweb.com.
You then log into your DNN install as a HOST (superuser) user. You can't do this from using the Admin Login for www.myweb.com, that admin won't have the permissions to add a portal. When you do login as Host, you'll see two more menu items appear, 'Admin' and 'Host'. Admin pertains to functions you want to accomplish ONLY on www.myweb.com, the Host menu applies to the ENTIRE DNN install, including ALL portals you've setup.
Depending on your version number, you probably will see either 'Portals' or 'Site Management' (if it's a newer install, like 6.0+), once you click on or drop the HOST menu.
From there you fill out the specifics regarding your new www.youweb.com website, including the url and any aliases you want. Once you do that and the DNS propegates, you'll then be able to go to www.youweb.com and login and set that site up.
Step #2 is talking about adding a binding in IIS, not doing anything in DNN. You need to tell IIS about strategicplanning.mysite.com, so that it will send requests for that URL to your DNN site.
So, the process looks like this:
Make sure that the DNS record for strategicplanning.mysite.com points to your web server's IP address.
In IIS, update the host header bindings for the current application to include strategicplanning.mysite.com.
a. If you only have one portal in your DNN installation, at this point, trying to navigate to strategicplanning.mysite.com will automatically add it as a portal alias for that one portal.
b. If you have multiple portals in your DNN installation, at this point, trying to navigate to strategicplanning.mysite.com will show an error message about that URL not corresponding to an existing site.
In DotNetNuke, you need to go to the Site Management page in the Host menu (previously called Portals), and use the Manage/Action menu to add a new site. In the form that comes up, use strategicplanning.mysite.com as the alias (keep it marked as a parent portal), and fill in the rest of the details. If you want a blank site, make sure that you pick the Blank Website template (otherwise you'll need to delete a bunch of pages and modules you don't need).
This should be all that you need to do. If you navigate to strategicplanning.mysite.com and you see the original site, then strategicplanning.mysite.com has been added as a portal alias for that site, and you'll need to remove it (in Site Settings under the Admin menu).
I've created some new fields for users who register in admin/config/people/profile
since we are still building the site I want to port these out to a features module
but am completely unable to figure out how to do this? I thought it would be some
thing like Features >> [Create Feature] [Edit components] >> Variables but cannot
find my custom fields?
I named my new form Registration, and tried view sourcing and flipping through the
source with the find command but am unable to find it there either. Anyone know what
it might be called or under?
In order to unlock the profiles, I used this Administer user profiles in Drupal 7 method.
In case you hadn't figured it out yet, you can export fields by selecting the "Fields: field" component when creating your view.
By the looks of your URL you're not using the latest 7.12 core version? Currently the page to manage the fields for user profiles is located at "Administer > Configuration > People > Account Settings > Manage fields" (admin/config/people/accounts/fields) page, so you may need to update...
Did you create a profile or add the fields directly to the user entity?
With the drupal 7 fields API you don't need the profile module anymore in fact it's deprecated. Because of that I don't think their is features support for profiles