Ruby on Rails Thursday, July 11, 2019

I don't understand what your are actually trying to do with that.

"@p" is an instance of the Project class, "find_or_crate" is a method on active record relations, what do you expect "@p.find_or_create" to do? I guess you can define your own instance method on Project class to do whatever you want

what's the use of "@pt = @p.tasks.build(params)" on your example?


El jue., 11 jul. 2019 a las 16:20, tom (<tomabroad@gmail.com>) escribió:
HI,
i want to upload a has_many association. but instead of adding records, i would like to to incorporate first/find_or_create.

is that posible?

@p = Project.new(params)
@pt = @p.tasks.build(params)

@p.find_or_create ????

is that possible?


thx

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/CADQqhMfGyFMaVpiFcgLf7GweJC7dAnr87XDwtM2UVS70LiyVNg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/CAPS3bcDxCJQzQ%2BO8XToaSfeX%3D31Yg-0V867Ps%3DT-goTaGxs_aA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Ruby on Rails

HI,
i want to upload a has_many association. but instead of adding records, i would like to to incorporate first/find_or_create.

is that posible?

@p = Project.new(params)
@pt = @p.tasks.build(params)

@p.find_or_create ????

is that possible?


thx

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/CADQqhMfGyFMaVpiFcgLf7GweJC7dAnr87XDwtM2UVS70LiyVNg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Ruby on Rails Friday, July 5, 2019

I'm not sure what this has to do with Ruby on Rails. As far as I can tell, Dynamics 365 is a Microsoft accounting application. Rails is an open-source framework for building Web applications. The only place their circles cross is that you could probably build a similar application as Dynamics 365 with Rails.

Walter

> On Jul 5, 2019, at 7:09 AM, vijay kumar <vijayseo.rbt@gmail.com> wrote:
>
> Hello!
>
> I recently inherited a Dynamics 365 environment and am new to the system. I'm working on a new requirement to only allow certain users to view certain accounts. IE:
>
> Person A can only see account A
> Person B can only see account B
>
> This environment has a single business unit accessing a custom entity. After doing research, I've made the following changes:
>
> Created a new Business Unit as a child of the original
> Assigned user A to the new business unit
> Created and set user A with a single security role that only has Business Unit access the custom entity
> Assigned account A to this new business unit's default team
> Unfortunately, all views for this user are showing as empty. Here are some tests I've run to try and resolve the issue:
>
> Set all of the teams to have no security roles to avoid any permission crossover.
> Tried making a team outside of the default BU team with the same results
> Tried to individually assign a record to user A, which also does not show up in any view. Not sure why any records fail to show for this user.
> Set the security role for the user to global on the entity in question and that, of course, shows everything. Anything less than global will not display any records for this user no matter where they are.
>
> --
> You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
> To post to this group, send email to rubyonrails-talk@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/12275cab-b693-4164-b6c7-94e3866acd05%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/B9524206-E921-4D5E-8CAC-8C7F4E5B0D85%40wdstudio.com.
For more options, visit https://groups.google.com/d/optout.