I have a website that it has more than 50 menu items. I want to add a functionality to the website by which, users be able to choose his/her most frequent menu items and add them on the right side of the main page. It can help the user to find links easily.
How can I do this or what's your suggestion to accomplish this in the best way?
Thanks
My Suggestion over this, is Create New SQL table, with Column UserID, and FavMenuItemID.
Create Table userFavMenuItem(
UserID INT,
FavMenuItemID INT
)
Do not forget to add foreign key constraints for both these columns.
So once user choose any Menuitem as Favorite, add a new row and when user want to delete any menu item, delete from this table based on UserID, and FavMenuItemID.
Now, to show Current Favorite menu items on right hand side, Just Get Favorite Menu itmes from this table using UserID.
EDIT
You have to create new page, where user can choose their Fav Menu Item(add/Delete), and also change their previous Fav selection also (at most user can have 5 Fav menu items), and also restrict user to choose only 5
Related
I have a master/detail relation similar to the relations sample provided.
In my example department has a one to many relationship with employee
I have a form widget(department) which has a button to insert an employee.
when I click on that button the correct dialog form is displayed but I am allowed to enter any department which I do not want.
I am looking to have the relation defaulted to the "parent" widget where it was clicked and ideally not be editable.
It's hard to give an exact answer without seeing your app, but you should probably replace the dropdown in the form with a label, that will make it not editable. You can bind the value of the label to the relation just like the value of the dropdown was bound.
A slightly easier option would be disabling the dropdown (look for the Enabled probably in the property inspector). But that could be confusing for your users since they might think it should be editable.
(Alternatively, you could just remove the field altogether if it's not important to show the relation.)
I think this only answers the "not editable" part of your question, if you want it to be pre-filled you either need to do some scripting, or use relation data sources.
I suggest using relation data sources, so right now you probably have something like:
app.datasources.Emp.create(), which creates a new employee.
Instead, you can use widget.datasource.relations.Emp.create(), which will create a new employee which has a relation to the current item in widget.datasource. If this button is placed in your department form widget, then that means it will create an employee related to whatever department is shown in the form.
Note that none of this stops users from changing the department of an employee, it just changes the UI. In lots of cases that is enough, but you may also want to add some server-side security controls if it's important to limit which users can create employees, change departments, etc: See https://developers.google.com/appmaker/security/secure-app-data
I have a requirement to have two custom record types under parent subtab arrange in order. I used parent-child relationship but the arrangement of the child subtab is something I couldnt customize. 'test one' and 'test two' are my custom record types, and Parent is item fulfillment record.
I want 'test one' to come first and then 'test two'.
I tried adding a new Subtab via customization under translation and this order customization is not available in netsuite. Am i missing anything?
Please help.
Edit the record
Click "customize" then "customize form" in the top right of the form
Navigate to "Lists" then select "Communication"
You can drag and drop your prefered order from this screen
Name then save the custom entry form
You can then manually select this form for the record or set it as the default form
If a field is visible on the form, then it appears somewhere in the Custom Entry Form screen. Which tab it's on depends on the type of field. It could be under Lists, or Fields, or elsewhere. Look for it.
When you find it, use the Field Group dropdown to move the field between the main view and sub tabs, and drag/drop the field to change its top-down display order. The drag handle looks like ⋮⋮.
I'd like to ask a tricky question to you about Drupal.
I created a new content type which includes lots of fields.
I want to find a module that adds a 'Add another' link to the adding content screen which will duplicate certain fields.
Example:
I have fields named Panel1 Photo, Panel1 Info, Panel2 Photo, Panel2 Info...
When adding a new content of this type, if I want to enter 3 panels, I want this module to create 3 fields of Photo and Info for me, and maybe 4 or 5 at other times.
I hope you will understand what I ask.
Thank you in advance.
You could have each field set to allow multiple values which would put the add another button you talk about. If you make a field collection with the field collection module you will be able to group those fields together and you can allow multiple values for the field collection. Let me know if you haven't found the add another button.
Install the field collection module then in the content type create a field collection with panel and photo fields.
When you create your first content page you will start with one panel and photo and a + button. The + button gives you the ability to create ever more panels and photos grouped together.
i would like to add a text box on top of the Dynamics Ax 2009 interface, that allow users to filter menu name.
Dynamics Ax has a 'big interface' with a lot of menu, sub menus etc. It would be nice to allow users to filters and visualize only filtered menu item .
Thanks
You will have to create your own toolbar instead of usual AX menu.
You can create toolbar with text field at the top and tree control that will represent filtered menu.
On load of toolbar you can scan menus at AOT and cache placement and labels.
When user enters some text to filter field you will rebuild your tree control according to matching.
There already is similar tool, but unfortunately I forgot it's name.
I have a very simple webforms app that will allow field techs to order parts from the warehouse.
Essentially it work like so:
User selects a category from a filter dropdown, which then binds items of that category to a gridview control
User finds an item in the gridview and inputs a desired quantity (in a text box in a template field in each row)
User repeats 1 & 2 as needed
User sees a summary of the complete requisition
User confirms items and submits the requisition for processing
My no-brainer UI design so far is the generic dropdown-above-a-gridview where there's a category drop-down list that filters a gridview, like in the eye-catching asp.net ado tutorials:
http://static.asp.net/asp.net/images/dataaccess/15fig01vb.png
Each gridview row (in my app, not in the image above) lists an item's details and can accept a quantity input in the template textbox if the user wants to requisition that item.
Given that a user will want items from different categories during a single usage session, I'm trying to figure out a good, user-friendly way to allow users to input a quantity for an item, have a warm fuzzy feeling that their input has been accepted/stored, then change the category filter (thus binding the gridview to a different set of data) and select other items from the gridview as many times as necessary before summing up their order and submitting it.
I've thought about putting another grid below the first and adding items to it dynamically as the user selects each item. But that seems awkward. Ditto with an unordered list or similar simple structure under the grid.
I've also thought about just storing the user's picks in view state or session state and displaying a summary on another page, kind of like a shopping cart sort of functionality. Maybe do that and use some sort of ajaxy goodness on the main page to display something warm and fuzzy when a quantity is input?
WWYD? What Would You Do?
TIA.
I strongly agree with your first choice: users need to see somewhere what they have chosen or they will probably keep choosing it over again thinking it failed. Waiting to display it on a summary page shouldn't even be an option. I don't see much wrong with binding to another grid, although a repeater is also a decent option. Well, there are many options. Anyway, if there is room to do this off to one side or another - especially the left- I definitely would, rather than at the bottom. Also, bonus points for enabling users to change the quantities (or delete all) of an item they already selected, wherever you choose to display this.
I like the idea of a search, but be careful with auto-complete. Google style is good where it displays results below, but I've seen people develop some that are way too aggressive and love to write over what you're typing: this is awful. Good luck.
Probably because both your choices are fine - it comes down to personal preference. The shopping cart idea is well known. But sometimes it gets old if you have to keep going back and forth between the cart and the item selection.
What's wrong with the separate grid? -That way you keep the selection list separate from the ordered items list?
Why tie the user to selecting the correct category and then selecting the quantity and hitting a button?
Why not use some type of autocomplete search so they can type in the produce name they want? Then a user could type "widg", get a drop town of choices, hit tab to go to a quantity field, enter a number, and then hit enter.
Display a quickie preview with the aucocomplete too, like as single row of your data.
Then throw all these into another grid at the top of the page if its a critical part of the application, maybe at the bottom if you think the actual grid results are important.
The reason I don't like category drop downs is people who are familiar with their jobs or company usually know the names and even skus numebers for what they are trying to do. Having them select a category instead of typing just slows them down. Also I hate running into the "which category is this?" moment. For example, is a chicken a pet, food, livestock, or food producer?