Is there a way to create a trash list?
Since I need to use soft deletes on my models I really need to create that list for the user restore tem items if he needs it.
I search in the docs but didn't found anything about it
You might try creating a View in your database that represents the soft deleted (trashed) rows. Then register a resource in your app for that view. You could actually UNION a number of tables together that had soft deleted rows in them as long as you could get some common columns from each table in your view.
After you had this view and tested it out, you could hook a to this view resource and let users view these deleted items. You could then connect an action to the List such that they could un-soft delete a given row.
Related
I have created a task manager view in Microsoft Outlook which contains user defined fields as well as other Pre-defined fields in the view. I am trying to share this task manager with the rest of my team however, I cannot get it to show all of the columns as they appear on my screen on their screens. I am able to share the task manager but many of the columns are missing. It seems to be because the custom view I created isn't being shared with the other users. On my computer, the custom view is displayed and selected above "Simple list" under the Current View menu on the left and the others do no seem to have that as an option. Does anyone know how I can share the view? The tasks are already being shared I just need the View to be shared so my team can see all the columns properly. Thanks for any input you may have to offer.
Views are defined and customized using the View object's XML property. The XML property allows you to create and set a customized XML schema that defines the various features of a view.
Use the CurrentView property of the Explorer or Folder classes to customize the View in Outlook. An XML definition of the view can be exported and transferred to another PC.
Ok essentially what I did was I went to view - current view - define views and created a new view selecting Table and This folder, visible to everyone. Then I found pre-definied columns that weren't user defined columns that allowed free text typing like subject, milage, and billing information. Once finished adding all the columns I needed I applied the view. Then I went and changed the name of the columns by right clicking each column header in the task manager and selecting format column. there you chan change the label name to whatever you want the column to be titled. This way you did not have to worry with using user defined columns that can be tricky to share. After that I went back to view - current view - define views, and made a copy of the view I created selecting this folder, visible to everyone. Then you will want to right on the tasks manager name you created under the My Tasks list and select properties. Make sure to give everyone your sharing it with full permissions as owners so that they can all edit the task manager as they finish each task. Then I shared this task manager by right clicking on the name of my newly created tasks manager (listed under the My Tasks menu) and selecting "share". I checked the box in the email stating recipient can add, edit, and delete items in this tasks folder. Now everyone can see all information displayed in each column and edit it as well hope this helps.
Google announced this feature today, but I don't see any docs for it. How can I grant row-level permissions to a user?
For example, let's say I have a table private.all_customers with the schema {customer:string, id:integer, is_secret:boolean}.
I like to give our salespeople access to the fields customer and id, but not is_secret, and moreover, I'd like to give to give them access to only those rows where is_secret = false. How can I accomplish this?
The key part of row-level permissions is that you're actually giving permission to a view. The view defines the rows and columns in that you want the delegated user to see, without giving them access to the underlying table.
To do this, create the view that will return the rows and columns that you'd like the user to see. For the example above, the view would look like:
SELECT customer, id FROM private.all_customers where is_secret = false
Then I can save this as the view "public.public_customers", and share the public dataset with the analysts.
Note that, so far, this does NOT mean that the analysts will have access to the data. If they try to run it now, they'll get an error. Merely having access to a view that reads a table doesn't give you access to the underlying data on that table. If it did, then anyone could just create a view to read any data that they wanted to see.
The second step is adding that view to the ACL of the private dataset. What this does is records that the view should have access to the data. This way the owner of the private dataset can audit who has access to their data, and revoke it if necessary.
The easiest way to add the view to the ACL is to use the BigQuery Web UI. If you click on the arrow next to the private dataset name in the Web UI and click "Share this dataset", it will bring up a dialog box that lets you edit the ACL.
At the bottom of that dialog it will show "Add People" and a clickable icon on the left. If you click on that icon, you should be able to select "Authorized View". Once that is selected, you should enter the fully-qualified name -- project:dataset.view of the view. In our example, that would be my-project:public.public_customers. Hit 'Add' and it will show up in the list, and then hit "Save Changes" to commit.
Once the view has been added to the ACL, anyone with access to the 'public' dataset should be able to run queries against the public.public_customers view.
For more advanced usage of this feature, which will allow you to give different answers to different users, see this question: How do I give different users access to different rows without creating separate views in BigQuery?
I have created a form for use during a meeting. Multiple people need to click approve at the same time. The issue is if they all are in the form at the same time, it is only going to keep the last approval and resets the fields the others have approved... as there approval was not there when the form was opened. I guess I should have seen this coming. Is there anything I can do?
Use two lists with a parent/child relationship.
You need a master list with a unique ID and a detail list where the Master ID is assigned to the new list items to define the relationship. In the Master List you can customize the display form to contain a list view of the related items in the Detail list and a link to add new items to that detail list. A little bit of JavaScript will ensure that a new item in the Detail list gets the Master item's ID assigned automatically.
Clear as mud? The SharePoint Hillbilly has a video tutorial for 2007 and 2010.
If you go through the material (the 2007 stuff is good to understand the approach), you'll find that there are two techniques, one using SharePoint Designer, the other one without SPD.
Back to your meeting: Before the meeting, create an item in the Master list. Everybody can see the item on their screen and click to create a related item in the Detail list. They can all save their related item at the same time, since these are individual list items in the Detail list. Refresh the display view of the Master list item to see everybody's replies.
I am just getting started with obj-c programming and cocoa.
Here is what I am trying to accomplish and have gotten stumped on.
I have a single table view of managed objects in Window1. I have a "Add Items" button that calls Window2 that has another blank table view (AddItemsTableView) and a series of form fields a user could fill in.
When a user fills in these fields and clicks an add button in Window2, the string values of said fields are input into AddItemsTableView to show a running list of items they are preparing to add. When the finally commit the add, I would like that running list to instantiate as NSManagedObjects
Do I need to do this as a seperate entity within coredata created just for objects to be added, then transfer the objects to the new entity upon the add action? Do I need to save them in a mutable dictionary and convert the dictionary to managed objects?
It's important that the addItemsTableView only contains data for the time period the window is open. When Add is commmited, the window closes and the table bound to the core data entity in Window1 updates with new results. If Add Items in Window 1 is pressed again, Window2 is called with an empty tableview again.
I've been searching through SO and other forums for days trying to find someone attempting to do the same thing. Can anyone point me in the right direction?
Thank you so much!
Connect your add table view to the original table view via a delegate #protocol so it can inform the other on its state and enable it to react accordingly.
Of course you use the same type of managed object throughout, no interim objects such as dictionaries. When the added data is saved, you could send the object back to the original table to be processed.
(Alternatively you can save and rely on e.g. the fetched results controller delegate - but maybe that is too advanced at this stage.)
I have a map to which features can be added and removed and am using an extjs 4 grid panel as a view (MVC) to list the features. The idea is that the user can click an item in the grid and highlight it in the map, click a button to remove it etc. The features do not have a natural key so I need to make one up, just a number is fine. At the moment the map starts up with some features already on it so I am able to loop through and give each an id and add a record to the store for each to tie the 2 up, but ideally I want the store to take care of that when each record is added. I also have the problem that when a new feature is created I need to get a fresh new id to use but I'd rather not have to loop through all my features to find the highest id.
I am using myStore.add({id:1,name:'blah'...}) to add the records - should I be using this or insert?
Any help appreciated
Yes you can use the store last to figure out your last record, but my recommendation is to handle ID generation to the server side. Typically database sequencer is used to create IDs.