## Efficient method of representing bijections

Let’s say I have to map the elements $$\{1,2,3,4,5\}$$ to $$\{a,b,c,d,e\}$$ as follows.

$$\{ \space \{\space(1,a) , (2,b) , (3,c)\space\} \space , \space \{\space(1,a) , (2,c) , (3,b)\space \} \space \} \space \times \space \{\space \{\space(4,d),(5,e)\space\},\space \{\space(4,e),(5,d)\space\}\}$$.

Thats basically a set of permutations as below
$$\{\ \space \{ \space (1,a), (2,b), (3,c), (4,d), (5,e) \space \} \space,\ \space \{ \space (1,a), (2,b), (3,c), (4,e), (5,d) \space \} \space,\ \space \{ \space (1,a), (2,c), (3,b), (4,d), (5,e) \space \} \space,\ \space \{ \space (1,a), (2,c), (3,b), (4,e), (5,d) \space \} \space \ \}$$

This was an for a set of 5 element bijections. My questions is that, in general for an $$n$$ element bijection set, is there any efficient method of representing or storing them.

## REST call in workflow throws Error The parameter URL does not exist in method Add

I have a workflow that created new sub-sites up until yesterday when it stopped working and started throwing the following error:

The parameter URL does not exist in method Add.

That parameter existed yesterday!

I haven’t changed anything in the workflow as far as I know.

The workflow is using the /_api/web/webinfos/add to create a new sub-site.

Has anyone else encountered this error?

## Namimg Methods – How to name method with complex execution sequence?

This question: https://stackoverflow.com/questions/1866794/naming-classes-how-to-avoid-calling-everything-a-whatevermanager contains many examples of suffixes and prefixes that can be used to come up with precise name for your class.

What about methods? For example, how to name a method that should execute some action upon validation of some state – ExecuteIfSomething, if we imagine that some transition in state should be executed after checking if something is true – ValidateTransition (kind of ok, but reading it makes me think that it should just validate something – not additionally execute some action), TranslateUponValidation?

It would be very useful to have list of common parts that can be added to action/topic/… to describe method.

Here are some that I can come up with at the moment:

• Get
• Set
• Contains
• Remove
• Push
• Pop
• Clear
• Close
• Lock
• Open
• Unlock
• Enqueue
• Dequeue
• Activate
• Deactivate
• Translate
• Move
• Jump
• Fill
• Empty
• Draw
• Take
• Give
• Stash
• Group
• Shuffle
• Mix
• Sort
• Merge
• Inline
• Validate
• Check
• Execute
• Apply
• Compose
• Decompose
• Decay
• Break
• Gather
• Fuse
• Grow
• Rise
• Drop
• Fall
• Pick
• Select
• Accept
• Decline
• Retire
• Increase
• Decrease
• Stop
• Continue
• Pause
• Resume
• Process
• Create
• Destroy

Maybe, I have put too many of them.

As you can see now – many if not almost all verbs can be used depending on the situation. Using them or finding the matching one shouldn’t be a problem. The problem is on how to combine them or use some of them to describe complex situations or complex executing sequence. The one I have described as an example is the most common one that I haven’t found a good solution for. Personally I am interested in this particular one. But having some way/approach (not a formula like Object + Action + …) to define/come up with method/function names can be very useful.

Main question here is how do you name a method as the one described in the example? It might seem to be a duplicate of this question – Meaningful concise method naming guidelines – I can clarify and update my question if that is going to be required.

## Namimg Methods – How to name method with complex execution sequence?

This question: https://stackoverflow.com/questions/1866794/naming-classes-how-to-avoid-calling-everything-a-whatevermanager contains many examples of suffixes and prefixes that can be used to come up with precise name for your class.

What about methods? For example, how to name a method that should execute some action upon validation of some state – ExecuteIfSomething, if we imagine that some transition in state should be executed after checking if something is true – ValidateTransition (kind of ok, but reading it makes me think that it should just validate something – not additionally execute some action), TranslateUponValidation?

It would be very useful to have list of common parts that can be added to action/topic/… to describe method.

Here are some that I can come up with at the moment:

• Get
• Set
• Contains
• Remove
• Push
• Pop
• Clear
• Close
• Lock
• Open
• Unlock
• Enqueue
• Dequeue
• Activate
• Deactivate
• Translate
• Move
• Jump
• Fill
• Empty
• Draw
• Take
• Give
• Stash
• Group
• Shuffle
• Mix
• Sort
• Merge
• Inline
• Validate
• Check
• Execute
• Apply
• Compose
• Decompose
• Decay
• Break
• Gather
• Fuse
• Grow
• Rise
• Drop
• Fall
• Pick
• Select
• Accept
• Decline
• Retire
• Increase
• Decrease
• Stop
• Continue
• Pause
• Resume
• Process
• Create
• Destroy

Maybe, I have put too many of them.

As you can see now – many if not almost all verbs can be used depending on the situation. Using them or finding the matching one shouldn’t be a problem. The problem is on how to combine them or use some of them to describe complex situations or complex executing sequence. The one I have described as an example is the most common one that I haven’t found a good solution for. Personally I am interested in this particular one. But having some way/approach (not a formula like Object + Action + …) to define/come up with method/function names can be very useful.

Main question here is how do you name a method as the one described in the example? It might seem to be a duplicate of this question – Meaningful concise method naming guidelines – I can clarify and update my question if that is going to be required.

## Namimg Methods – How to name method with complex execution sequence?

This question: https://stackoverflow.com/questions/1866794/naming-classes-how-to-avoid-calling-everything-a-whatevermanager contains many examples of suffixes and prefixes that can be used to come up with precise name for your class.

What about methods? For example, how to name a method that should execute some action upon validation of some state – ExecuteIfSomething, if we imagine that some transition in state should be executed after checking if something is true – ValidateTransition (kind of ok, but reading it makes me think that it should just validate something – not additionally execute some action), TranslateUponValidation?

It would be very useful to have list of common parts that can be added to action/topic/… to describe method.

Here are some that I can come up with at the moment:

• Get
• Set
• Contains
• Remove
• Push
• Pop
• Clear
• Close
• Lock
• Open
• Unlock
• Enqueue
• Dequeue
• Activate
• Deactivate
• Translate
• Move
• Jump
• Fill
• Empty
• Draw
• Take
• Give
• Stash
• Group
• Shuffle
• Mix
• Sort
• Merge
• Inline
• Validate
• Check
• Execute
• Apply
• Compose
• Decompose
• Decay
• Break
• Gather
• Fuse
• Grow
• Rise
• Drop
• Fall
• Pick
• Select
• Accept
• Decline
• Retire
• Increase
• Decrease
• Stop
• Continue
• Pause
• Resume
• Process
• Create
• Destroy

Maybe, I have put too many of them.

As you can see now – many if not almost all verbs can be used depending on the situation. Using them or finding the matching one shouldn’t be a problem. The problem is on how to combine them or use some of them to describe complex situations or complex executing sequence. The one I have described as an example is the most common one that I haven’t found a good solution for. Personally I am interested in this particular one. But having some way/approach (not a formula like Object + Action + …) to define/come up with method/function names can be very useful.

Main question here is how do you name a method as the one described in the example? It might seem to be a duplicate of this question – Meaningful concise method naming guidelines – I can clarify and update my question if that is going to be required.

## Namimg Methods – How to name method with complex execution sequence?

This question: https://stackoverflow.com/questions/1866794/naming-classes-how-to-avoid-calling-everything-a-whatevermanager contains many examples of suffixes and prefixes that can be used to come up with precise name for your class.

What about methods? For example, how to name a method that should execute some action upon validation of some state – ExecuteIfSomething, if we imagine that some transition in state should be executed after checking if something is true – ValidateTransition (kind of ok, but reading it makes me think that it should just validate something – not additionally execute some action), TranslateUponValidation?

It would be very useful to have list of common parts that can be added to action/topic/… to describe method.

Here are some that I can come up with at the moment:

• Get
• Set
• Contains
• Remove
• Push
• Pop
• Clear
• Close
• Lock
• Open
• Unlock
• Enqueue
• Dequeue
• Activate
• Deactivate
• Translate
• Move
• Jump
• Fill
• Empty
• Draw
• Take
• Give
• Stash
• Group
• Shuffle
• Mix
• Sort
• Merge
• Inline
• Validate
• Check
• Execute
• Apply
• Compose
• Decompose
• Decay
• Break
• Gather
• Fuse
• Grow
• Rise
• Drop
• Fall
• Pick
• Select
• Accept
• Decline
• Retire
• Increase
• Decrease
• Stop
• Continue
• Pause
• Resume
• Process
• Create
• Destroy

Maybe, I have put too many of them.

As you can see now – many if not almost all verbs can be used depending on the situation. Using them or finding the matching one shouldn’t be a problem. The problem is on how to combine them or use some of them to describe complex situations or complex executing sequence. The one I have described as an example is the most common one that I haven’t found a good solution for. Personally I am interested in this particular one. But having some way/approach (not a formula like Object + Action + …) to define/come up with method/function names can be very useful.

Main question here is how do you name a method as the one described in the example? It might seem to be a duplicate of this question – Meaningful concise method naming guidelines – I can clarify and update my question if that is going to be required.

## Jquery autocomplete. undefined method

Estoy implementando Jquery Autocomplete. Pero me arroja el siguiente error:

undefined method product_pro_nombre’ for #Did you mean? product_id_change

mi vista _order_detail_fields.html.erb

    ...     <%= f.hidden_field :product_id, id: 'temp_id', disabled: "disabled" %>     <%= f.autocomplete_field :product_pro_nombre, autocomplete_product_pro_nombre_order_details_path, 'data-showNoMatches' => false, class: "form-control producto", :id_element => '#temp_id', onchange: "setValue(event)" %>     <%= f.hidden_field :product_id, class:"product" %>     ... 

Funciona bien el autocomplete si en lugar de :product_pro_nombre lo dejo como :product_id. Pero al momento de recuperar esta vista para hacer un UPDATE, en lugar del nombre del producto me muestra el ID. Entiendo el porque del error, ya que el product_id es una llave foranea de OrderDetail. Pero no encuentro la forma de recuperar el nombre.

Esta es la documentación que estoy siguiendo https://www.rubydoc.info/gems/rails-jquery-autocomplete/1.0.5

## Rest API Error : The Parameter accept does not exist in method

I am using SharePoint designer to execute an Rest API call.

I know my workflow itself works because I can enter a different REST call and it works.

My URI is :

http://thishsarepoint.sharepoint.com/_api/web/lists/GetbyID(guid'xx-xx')/items(8)/file/copyTo(strNewUrl='https://thissharepoint.sharepoint.com/doclic/jokers.csv',bOverWrite=true) 

And the error is The Parameter accept does not exist in method CopyTo`.

I am using SharePoint designer workflow.

Any help would be awesome.