Personalize

[Søren Dyhr]

I have an ugly hunch that something is staring my in the face here?

In a CRM system, which have a company table and a related table of contacts, but according to who is opening and viewing each company record, should his/her contact in the company be sorted up into to the first portal line, due to it's use in letters/quotes/invoices.

This means that login defines the sortorder for each record, further more should a "swap" button be attached to each portal line, making it posible to switch another further down up to the significant position as reciever of posts.

Since we're in a multiuser solution can't data just be swapped via $variables and is BTW relatioal unhealthy, say another user is printing a series of letters and your dealings as user tampers with his choise of attention ...neither is it personalized via the login any more.

I should be said that I have a solution to the problem that works, but it's way too complicated to be true - hence the post here!

--sd

[Genx]

Why not use globals to define both the specific letter that the user is printing and / or the focus?

I employ both methods fairly easily.

[Søren Dyhr]

I employ both methods fairly easily

So could I - but are globals as such endorsed anywhere in the developement world? They are usually the source of lot's of grievance when reverting to server default when opened next time, do you really think a init-script and exit-dito as long as an arm is more relibale than hardwire such info to each record?

Globals are volatile and session-specific!!!!!!

Perhaps uploading the "going on"'s in a sick mind makes more sense? Feel free to suggest improvements!

--sd

reshuffle.zip

Edited January 23, 2007 by Guest