I have created a new view ("form") in my Access Web App using the menu buttons to create a new view. The view is bound to a table in my database. Running Access on my computer, I can select the view from the navigation panel on the left.
Now I would like to have a link to my view appear at the top of the page in the Web App. Much like the default List and Datasheet view that are created automatically for every new table.
How can I create a link to my view, so that I can select it when running my Web App in the browser?
(And in general: where's a good place to find documentation and help regarding Access Web Apps. I'm having a hard time finding anything online)
thanks for your help.
What entry point did you use to create this new view in your Access web app? If you used the Advanced button on the ribbon, that creates what we call a standalone view in your web app - a view that exists in the Navigation Pane in Access client. You can only open these types of views using macros.
In order to "associate" an existing standalone view to the View Selector at the top of the navigation, right-click the view name in the Navigation Pane and select Duplicate. a dialog box will appear that allows you to create an identical copy of the view and "associate" it with a particular table. It will then appear as a link in the View Selector. You can then delete the original view if you want.
Related
I have an app on retool and I want to try out some different layouts. Is there a way to duplicate an app or have version control that you can revert to?
You can duplicate an app by going to the "Create New App" screen, and then instead of selecting "Blank App" you can choose "Duplicate". That'll allow you to choose an existing app to copy from.
Revision History is possible by hitting the "..." button in the top right, and then selecting "View history".
Not sure if Retool updated their UI, but I wasn't able to do this with the accepted answer.
I needed to hover over the name of the app in the list view (before you actually edit the app) and click the ... button on the right. Then, I selected duplicate from that dropdown.
I have created a Sharepoint hosted app for Office 365. It has a page file "default.aspx". I have added an XSLTListViewWebpart on that page, referring a custom List I created within my APP project. I have a requirement that on a button click event, I need to change the View of the List displayed in the XSLTListViewWebpart. Since there is no server code within the APP, would this be possible in javascript? Or would it be possible to somehow change the query that the webpart uses?
You can try to use Javascript object model to achieve this. Please see this article.
I am trying to add a customised announcement list to the main page of my SharePoint site on this list, there will be 7 columns on the list but the challenge i'm having now is how to only display 3 out of the 7 columns on the site and the other columns will only be displayed when user clicks on add new announcement or clicks on the list itself. Please can anyone give me an idea of how to achieve this.
E.g: Assuming i customised an announcement list to have column: management, operations, Assets, Finance,HR,QHSE and Technical and added it on my SharePoint page via web-part, How can i make it to only display 3 of the 7 columns like management, operations, Assets while other columns will only be seen whenever users click on the add new announcement or go directly to the list itself. Thanks
For displaying only 3 columns, create a view and set it in the webpart options.
When you create a new view of a SharePoint list, it essentially creates a new .aspx page with the view customized per your definition. This can be done for standard views easily from the SharePoint list's web interface. This is the suggestion from Le_Freddo and should work for creating custom views but not for creating custom edit pages.
For that I believe you need to use SharePoint Designer. Open the site in SharePoint Designer then locate the list you're working on under 'Lists' in the 'FolderList'. You'll see 4 pages, AllItems, DispForm, EditForm, and NewForm. Make a copy of the EditForm (before you modify it), then open the EditForm to make your changes to it. You can add or remove fields from the page. In this way you can customize the Edit form to show all fields or only a subset.
You can also use this method to customize the other views (removing columns you don't want users to see).
When you're done, you can direct your List to use the new pages or define which page to use for each operation (View-All, Display, Edit, Create New) by setting the List's properties (right click the list in the Folder View, select Properties, then the 'Supporting Files' tab will have links to the pages configured for these actions).
Good luck...
I am currently working with Siebel Call Center (Siebel Tools 8.1) and I'm having some trouble adding a tab to the top of the screen, where the 'Accounts', 'Contacts', etc tabs are.
I have added an item under the Page Tabs menu for the Siebel Universal Agent application, but the tab will only show up for the Siebel Administrator.
In Tools:
Create your Views and associate them to a Screen.
In OE go to Application, choose the desired application (e.g. Siebel Universal Agent) and expand. Choose Page Tab, create a new record with your screen.
Compile everything.
In Web Client:
Go to Administration - Application > Responsibilities, choose the responsibility and then Tab Layout, select the application (same as before), find your screen and uncheck the hide property.
Clear the Cache.
Log out.
Log in with the appropriate user.
This is likely because you have not associated any responsibilities with the tab.
This can be administered under:
Site Map > Administration - Application > Responsiblities > Tab Layout
More detail can be found here:
http://download.oracle.com/docs/cd/B40099_02/books/Secur/Secur_AccessControl40.html
When you say tabs at the top of the Screen I'm assuming you are referring to a Siebel Screen. You do not associate Screens to Responsibilities. You associate Views to Responsibilities. Because a View is a child of a Screen once a View is associated to a Responsibility the Screen will also become available.
You need to do a couple of things to get the Screen/View to be visible.
In the Object Explorer of Siebel tools make sure you have defined your View
In the Object Explorer of Siebel tools make sure you have defined your Screen
In the Object Explorer of Siebel tools make sure you have associated the View to the Screen
Take note of the View Name
In the Siebel Thin/Thick Client, navigate to:
SITE MAP > Administration - Application > Responsibilities
Make sure that a Responsibility that you are associated with has the View (noted in step #4) associated with it
Click the Clear Cache button.
Log Out and back In
Your Screen and View should now be visible.
Just to add to this...
If you are creating the new View from scratch... you'll need to add the View as follows:
Navigate > Site Map > Administration - Application > Views
In the Views Applet click NEW to and enter view name and view description
Set the Local Access flag to Y
In the Responsibilities applet underneath, specify a Responsibility to associate with the view and set Local Access flag to Y
Then you can navigate to Navigate > Site Map > Administration - Application > Responsibilities and clear the cache
i've a proect opening with user authentication page (asking username and password). There are some extra buttons here which the app navigate to a single page when the user clicks (up to that point there is no need for table view but from those sub screens app can navigte back to that main page). In addition, if user is authenticated then the app will navigate to a page which lists some items on it (table view) and then navigate to some detail views back and forward. And i also want my app to have core data support.
Navigation based or window-based are two major possibilities, aren't they?
thanks
It sounds like you are building a navigation based app. If you look at your app without the login page, it sounds like a textbook navigation based app. Generally a login page will be handled by just using presentModalViewController on top of your existing navigation controller.