Not sure whether I'm allowed, I will run that by my superiors. But I may be able to point you in the right direction. First of all, here is an example of how to create a string containing an ical file: [url=https://sqlqueen.wordpress.com/2011/04/25/create-ics-file-in-sql-server/]https://sqlqueen.wordpress.com/2011/04/25/create-ics-file-in-sql-server/ [/url] Where I use this, an e-mail is sent right after the ical file is created. Now dbmail is not able to send actual files, but it is able to send query results. So the way I do it is as follows: [list=1] [*]I query all my necessary parameters [*]I create a string which I fill with the parameters. [*]I build a query in text 'set nocount on; select ''@icalString'' '. Note the 'set nocount on' this is necessary, because otherwise the output will contain 'x number of rows affected' [*]I call sp_send_dbmail with the necessary parameters and the built string as query, note following fields in particular [/list][list] [*] @query
Only the active one. Are you trying to tell me "That's just how a selected field looks" ?
In my situation I feel that a dash just won't do, so instead I have tried a couple of options: null, '', ' ', char(0), char(0x200b).. But it turns out that a space actually gives me the smallest possible visible blue box, which to me has to do for now. Although I think it would be great if a label with value null would be hidden completely. To solve the 'selected node' issue, maybe the whole node (with or without label) can get the dotted border instead of just the label
Thanks for your response. I have to say I wholeheartedly disagree. Let me explain my vision on how the suggestion-contains lookup-control works. Situation 1: When a user knows exactly what he wants, he can type directly in the grid and automatically get the item he wants (this can be any of the items from the lookup). Situation 2: The user does not exactly know what he wants, he opens the pop-up of the lookup, there he can use prefilters to help him find the item he needs. When he has found the item he wants, he selects it and goes back to the grid. Next time he wants to enter an item it should in no way be affected by his previous (search) action. Let's think of a silly example: Let's say you're in a grid where you have to assign a person to a task. Now lets say you have a lookup with a prefilter for male/female. You want to assign a person and can't quite remember the name of the person, but you do know it's a woman, you prefilter for women and find the right person. You now clos
Hey Vincent, Thanks for your reply, this indeed is a valid situation as well. I think we agree that the prefilters shouldn't just reset whenever the pop-up is closed. But I think the solution is that typing in the grid should not be influenced by the prefilters at all (except for locked prefilters of course). This means that when the user knows the value he needs, he can type it and get the value no matter what. If the user is unsure he can open the pop-up and change the filters to his needs (whether they were reset or not). Now I can see a situation where user [b]thinks[/b] he knows what he needs and enters a value that does not fit with the prefilter he would have chosen.. But then the question is whether the prefilters are meant to help the user find an item or whether they are there to safeguard him from making mistakes. Although this could for example be solved quite easily by adding a small icon to the gridcell telling the user the autocompleted value does not comply with the
Hey Vincent, I think your proposed solution will work better on the possible situations than the current solution does. Probably we will have some work to set the prefilters to fit this new situation, but after that I believe our issue will be solved. Thanks for thinking with me :D
Now that we are on the topic, might it be beneficial to put a grouping on the reserved keywords to make a distinction between (for SQL) reserved keywords, ODBC reserved keywords, future keywords... This would make it easier to determine whether the validation has to be followed or whether it can be approved
Indeed SQL does order it the expected way...
I think it would be nice if the elements then have a checkbox "include in generated prefilter". So if I have elements I don't want in my filter I can leave them out
Be careful with phone numbers, the notation varies per situation, local, national, international +31612345678 0612345678 (035)1234567 etc.
Agreed, everyone (at least every website) has this nowadays
I agree, but maybe it would be better if this is configurable. I think there is a very valid workflow where (almost) all interfaces are in fact views, in which case most of the views would be editable.
in HTML5 this is completely standard I believe, at least we are all used to it on the internet. So i agree with Mark this would be a very good addition to the SF
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.