Activities of "AlderCove"

Hi @mk2software

Your use case for Candidates isn't clear to me.

1. What is the relationship between a candidates and a customer/tenant?
2. Is a candidate for a specific customer/tenant? Or more than one tenant?
3. Should all candidates be managed within an instance of a single tenant (i.e. Candidate tenant)?
4. Is each candidate effectively its own tenant?

Can you describe your application a bit more to provide some more context.

Thanks Jamie

Hi @ismcagdas

It took a bit of refactoring, but we are all good.

Thanks

Thanks for your help @maliming, I'll do that and follow the thread.

Sorry, should have read _context.Clients.

I have it working now by grouping after the query is executed on the database.

        var query = _clientRepository.GetAll().Select(g => _clientReferralRepository.GetAll()
                                                                                    .OrderByDescending(p => p.Id)
                                                                                    .FirstOrDefault(p => p.ClientId == g.Id));

        var results = (await query.ToListAsync()).GroupBy(g => g.ReferralStatusTypeId)
                                    .Select(g => new
                                    {
                                        ReferralStatusTypeId = g.Key,
                                        ClientCount = g.Count()
                                    }).ToList();

Ideally, the grouping could be done on the database side rather than in memory.

Any thoughts?

Thanks

Hi maliming,

Here are the relevant bits.

Client:

    public class Client : FullAuditedEntity
    {
        public string Name { get; set; }

        public List<ClientReferral> Referrals { get; set; }
    }

Client Referral:

    public class ClientReferral : FullAuditedEntity
    {
        public int ClientId { get; set; }

        public Client Client { get; set; }

        public int ReferralStatusTypeId { get; set; }

        public ReferralStatusType ReferralStatusType { get; set; }
    }

Referral Status Type:

    public class ReferralStatusType : FullAuditedEntity
    {
        public string Code { get; set; }

        public string Name { get; set; }
    }

Thanks Jamie

ANZ 8.1 EF Core 3.1

Hi @maliming

I haven't seen any issues yet with the zero built-in code, just some of our own more complex joins.

Jamie

We integrated the SSRS report viewer with our Angular 7 Asp.Net core project. I'm not sure it would qualify as best practice, but it was a simple approach.

The approach used an iframe that referenced a local IIS website running a simple Asp.net application with the embedded report viewer control. This enabled reports to be run and viewed in the angular front end and required very little programming.

Our initial implementation utilized the SSRS web service to list the reports in the front end. We have since implemented a Report entity that holds the definition of the report, including a reference to the SSRS path and a permission name, so that it can be secured.

Hi @velu

We integrated SSRS with our aspnetcore/angular project and I am interested to learn how you implemented devexpress.

Can you please share your link.

Thanks Jamie [email protected]

Great job!