How to push items to the top or bottom of the list in alphabetically sorted lists?

This question is not related to any specific scenario, platform or product, and it’s more of an end-user UX rather than a design of UX. It applies to various use cases and platforms. One specific example which prompted me to ask this question is the notebooks list in Evernote – I’d like to push my notebook called “Archives” to the bottom of the list – it’s right at the top otherwise. Another cases are naming the files and folders on a computer.

There are certain lists which are sorted alphabetically and there’s no way to re-arrange them. In general, this is quite practical as it makes it easier to find the items when there are plenty of them and there’s no need to arrange them manually.

However, sometimes you want to push certain items on the list to the top or to the bottom. And the only way to do that is to prefix the item with a certain symbol.

So:

  • For pulling items to the top, the most common I’ve used is !, so your Requirements item becomes ! Requirements. Other nice options are ~ or -.
  • For pushing to the bottom however, one obvious symbol is “z”, so if the item is named Archives, you name it zzz-Archives or zzz Archives.

While the exclamation mark and other non-alpha symbols seem OK, I find zzz knocks off the visual “tidiness” of a list.

I am wondering if anyone used or seen more elegant solutions to pushing and pulling?

Attach flow dynamically to lists created by site design

I have a site design, that adds a SharePoint list with some columns. I need the ability to select an item from that list/library, and click on Flows, and choose my flow and run it.

The case I have is that the sites will be created by users, and the site design will be applied to them which creates those lists. Is there a way to attach the flow to those newly created lists so the Flow would appear in the list of Flows and bind it dynamically to it?

Remove Lists?

Just curious how extensive your remove list is — My list is growing of domains that I remove automatically.  Are you pretty liberal where you post?  

How do you go about creating your own remove list (blacklist??)?

Adding a many to many relationship, and having a form input data into two lists

I’m building a form for a Marketing Event list. The list would track name/type/location/date etc of the event and also those people associated with it (for example recipients or attendees) These people would be pulled from an existing contacts list, selected by whoever is entering the data for the marketing event.

I want to create a separate table to join so I can create a many to many relationship (I understand this is possible through Parent/Child links?) There would be the Marketing Events table, the Contacts table, and an intermediate table that consists of a foreign key-type relationship to each.

Here’s where it gets tricky; for the user entering the marketing event, I’d love for them to be able to filter contacts based on criteria (ex. a column having a certain value) then be able to have this filtered list input into the intermediate table. For example, if the filter comes up with five people that fit the criteria, add those five people to the intermediate table, using the name from contacts and the event name from marketing events.

Failing that, I’d at least like to implement something in the form to choose multiple contacts and add them to the list. Of course, this also means the form would be inputting into two lists, unless I had two seperate forms.

Hopefully this makes sense. Is this possible in Sharepoint? Is it all a pipe dream?

How can I upload information in PowerBI from Sharepoint lists of more than 5000 items?

We have a list that has exceeded the threshold of 5000 items. We want to do operations with PowerBI with the elements of that list but we are not able to load the information due to the threshold of 5000 elements. We are loading it through oData.

How can we do to get the list of more than 5000 items loaded into powerBI?

Any help will be appreciated.

Thanks

How does this allow list operations to be applied to lists with elements of any type?

In Types and Programming Languages by Pierce, Chapter 11 is simple extensions of the simply typed lambda calculus with any simple base types. Section 11.12 introduces Lists.

How does the section allow list operations to be applied to lists with elements of any type? Specifically, my confusions are:

  • Does Section 11.12 introduce lists and list operations by making use of some kind of polymorphism, or type inference? (The book doesn’t introduce type inference till Chapter 22 and parametric polymorphism till Chapter 23.)

    Does “When we first introduced lists in §11.12, we used “custom” inference rules to allow the operations to be applied to lists with elements of any type” in Section 23.4 mean that Section 11.12 makes use of type inference to achieve similar behavior of “polymorphism”?

  • Does “For every type T, the type List T describes finite-length lists whose elements are drawn from T” in Section 11.12 mean

    • that List T is a single literal type name for all possible specific typess for T, or
    • that List T should be instantiated differently for different specific types for T, e.g. List Boolean, List Nat?
  • Is [T] part of the the names of the list operators, e.g. nil[T], cons[T], isnil[T]?

    Should [T] in nil[T] be instantiated differently for different specific types for T, e.g. nil[Boolean], nil[Nat]?

  • Does Section 23.4 use the same type List T as in Section 11.12? Where is List T defined?

  • I think lists are not simple types but recursive types (not introduced till Chapter 20), so why does Section 11.12 cover lists?

Thanks.

11 Simple Extensions

11.12 Lists

The typing features we have seen can be classified into base types like Bool and Unit, and type constructors like → and × that build new types from old ones. Another useful type constructor is List. For every type T, the type List T describes finite-length lists whose elements are drawn from T.

Figure 11-13 summarizes the syntax, semantics, and typing rules for lists. Except for syntactic differences (List T instead of T list, etc.) and the explicit type annotations on all the syntactic forms in our presentation, these lists are essentially identical to those found in ML and other functional languages. The empty list (with elements of type T) is written nil[T]. The list formed by adding a new element t1 (of type T) to the front of a list t2 is written cons[T] t1 t2 . The head and tail of a list t are written head[T] t and tail[T] t. The boolean predicate isnil[T] t yields true iff t is empty.

enter image description here

and

23 Universal Types

23.4 Examples

Polymorphic Lists

As an example of straightforward polymorphic programming, suppose our programming language is equipped with a type constructor List and term constructors for the usual list manipulation primitives, with the following types.

ñ nil : ∀X. List X cons : ∀X. X → List X → List X isnil : ∀X. List X → Bool head : ∀X. List X → X tail : ∀X. List X → List X 

When we first introduced lists in §11.12, we used “custom” inference rules to allow the operations to be applied to lists with elements of any type. Here, we can give the operations polymorphic types expressing exactly the same constraints

I Can Find Out Targeted Niche Active And Valid Email Lists For Email Marketing. for $5

HI! I’m here to give you 100% real, valid and concentrated on the email list (individual or business email). Here I am giving you a sample which is done on my own. Which is based on the make-money. This email summary forms your business traffic, thing arrangements, and others promoting purposes. I will physically accumulate the US, UK, Aus, Canada, etc based email list for you OR essentially promise me what type zone, catchphrases or claim to fame related email show you required. Advantage of this gig: 1. Gather mails. 2. High-quality Niche based mail. 3. Gathering mail dependent on your advantage. 4. Country-based mail. 5. Gathering mail dependent on your choice. (for example, USA, UK, AUSTRALIA). 6. 100% real and valid mail. 7. Mail administrator details. 8. Best mail for Business use. 9. No invalid emails, I don’t provide. 10. 100% perfect and on-time delivery. 11. You can use these emails for email marketing. 12. I will give you an active and good quality mail. 13. 100% Real Email. 14. I am really different from other sellers process and do it my own. You can place the order with confidence and feel free to ask me any question!!!

by: SEO954Alex
Created: —
Category: Local SEO
Viewed: 187


Sort Associations by its Values (which are nested lists)

I have associations where the values are nested lists:

assoclist= <|KeyA -> {{a,b,2},{c,d,4},{e,f,3}},  KeyB -> {{a,b,1},{c,d,4},{e,f,6}}, KeyC -> {{a,b,2},{c,d,6},{e,f,9}}|>; 

Now I need to sort the associations by the total sum of the third elements (here the numbers) in each list so that Key C comes first (total sum = 17), than Key B (11) and Key A (9).

How can I do this?

How to filter on all SharePoint lists with a particular word in the name of the list

I have many Document Libraries that have the word ‘Knowledge’ in them. For example New Jersey Knowledge Library, New York Knowledge Library, etc.

I want to pull back all of these libraries and add a view to them. what is the proper syntax in PnP Powershell to do this? If the view already exists I don’t want to add it again.

$  lists = Get-PnPList -Web $  web | Where-Object {'Knowledge' -in $  _.name}          foreach($  list in $  lists)         {           Write-Host "The name of the list is: " $  list.name                 $  views = Get-PnpView -List $  list                 if('Knowledge Library' -notin $  views.title)                 {                     Write-Host "Knowledge Library View was not found found in one of the titles" -ForegroundColor Red                     Add-PnpView -Title "Knowledge Library" -List $  list.title -Fields "Type", "Title", "Content Author", "Published Date", "Abstract" -ViewType None -SetAsDefault                     Write-Host "Created View for this Knowledge Library" -ForegroundColor Cyan                 }           }  }