I have a set of items displayed in page viewer web parts that are from an external site. In order for them to display login credentials for external site are needed. I put the login page as the first web part (page viewer) on the sharepoint library. how do I make it so that after login is completed the page refreshes automatically to now display the other web parts?
it is bit tricky, since here cross domain comes into picture, but probably what you can do is, have a button where in you show that page viewer for login, and once clicked you have some kind of timer, which then refreshes the other page viewer urls. To refresh url is easy just reset the "src" attributes of iframes.
Related
I would like to add a custom page to a side panel in Acumatica. For example, if the page redirects automatically to an external website, I want that to be the view the user sees when they load the side panel (without having to click a link through a GI, for example).
Is this doable? Does anyone have specific instructions on how to do it?
In my scenario there is a HTML web form that user fills it and after pressing submit button it redirects to another custom page, I want to instead of redirecting to another page redirect to my Flutter app and read some page parameters. Is it possible?
Is there a way to open a the following page programmatically using Xrm as we can open forms or dialogs ?
Sort of, but I'm not sure its supported, the search page is presented as part of the main.aspx page. There is no obvious option to force the main page to open the search content documented.
However, if you open the search page, and debug the contents you can get a URL that points to the search page contents.
You could then append that address to your CRM URL and you will be redirected to the search page, however all the CRM menu bars are missing.
I.e. (note main.aspx is omitted) https://yourcrm.crm4.dynamics.com/externalsearch/externalsearch.aspx?option=0&sitemappath=projects%7cMyWork%7cnav_dashboards&text=
Is there a way to set the home/landing page for a SharePoint 365 site to the Site Contents page https://support.office.com/en-us/article/The-SharePoint-Site-Contents-page-ba495c1e-00f4-475d-97c7-b518d546566b
You could add a script on startpage in a script editor web part that redirect users to Site contents. That redirect surely will create a "flicker".This should do it:
window.location.href = "/_layouts/15/viewlsts.aspx";
Beware that this will be hard to remove from the web part (you will always get redirected), so maybe it should be added to a new page layout that is used by the startpage. Then it's possible to edit/remove the redirect through SharePoint Designer.
You could also try (if you have publishing feature activated) the "Welcome Page" link in site settings. Maybe there you could somehow point out the path to site contents, but I doubt it.
So I've setup a site collection using the Publishing Portal template and stubbed out a prototype site structure including three tiers. At the second tier I've created a Publishing site and developed a custom master page for the site and its third tier children. The problem is that the banner graphic on a few pages should be modified to be inconsistent. Then I add two new ContentPlaceHolder controls to my master page in SharePoint Designer and use the SharePoint interface to create my new publishing pages. Finally, I verify in SharePoint Developer that they have the correct master page, add my asp:content controls to the pages and insert the page-specific banner graphic. The only problem is that the master page default content continues to be rendered in all page instances. If I create a new page from the master page in SharePoint designer, I get a different base class in the Page declaration than those created within the Publishing site. Do publishing sites ignore any non-SharePoint contentPlaceHolders?
There is nothing like SharePoint ContentPlaceHolders & non-SharePoint ContentPlaceHolders. When you add a Default content to the Master Page ContentPlaceholder and if you dont override it in the Content Page then it will be visible in all the Pages that use that Master Page. Only way to get rid of it is to Override those Content Place Holder with empty content in the Content Pages. As overriding contentPlaceHolder in all the Pages is not an good Aproach. What I recommend is not to place conent in the ContentPlaceHolder of the Master Page but instead , put the content in the Content Control page of the Pages, so that Content doesn't come in all page but only the page that needs it. Yes it not a good to put the exact same content in multiple page. but in your case that is only the Option. May be you try to wrap the content in to a User Control so that the code can be updated only one place