First, SQL Complete allows for Intellisense similar to how it works in VS, in that Intellisense will display entries that "contain" the text being entered while Sql Prompt only displays entries that "start with" the text being entered. However, I found 2 things that set the devArt product apart from the RedGate tool. However, being on my own, they can be cost prohibitive so I went looking for less expensive alternatives, which is how I came across devArt SQL Complete.įrom my testing it looks like both have the same basic functionality. I love RedGate tools because they are solid and are very powerful.
This is the first time I have used this product but in the past I have used Sql Prompt from RedGate, which I would consider a competitor. It includes upgraded Intellisense (which allows you to replace the Intellisense included with SSMS) and T-SQL formatting tools. I just came across a pretty good product from devArt called SQL Complete that is an add-in for SSMS and VS. You could set up the primary SQL Text in the dynamic view definition, and then override in PeopleCode should the situation arise.I wanted to get other's opinions as well as share my own. Therefore, this could be a useful option if you have a prompt that works in a certain way the majority of the time, but just needs a small modification now and again.
In fact the ‘Build -> Current Definition’ option is greyed out completely for dynamic views.Īt run-time, if you don’t set the ‘SqlText’ property at all, the system will go back to the default text entered against the record definition. You can still set up SQL text against the record definition as you normally would for an SQL view:Īgain, there is no need to build the view, even with the SQL text entered. You will receive a run-time error if the field list is incomplete.įinally, one other feature of dynamic views is worth mentioning. For our Country dynamic view, we have specified two fields (COUNTRY and DESCR), so the SQL text must include those two fields. When the SQL text is set dynamically, the statement must contain the same number of fields as that of the record definition. Then, when the user clicks the prompt on the page, the dynamic SQL automatically takes effect: Using our country example, here is an example of setting the SQL text dynamically: RECORD_ = "select country, descr from ps_country_tbl " | This is usually added to a ‘RowInit’ or ‘FieldChange’ event (or often both).
Next, add code to the page to set the ‘real’ SQL text at run-time.
Because this record type does not require SQL text, it can be saved immediately once the fields have been configured. The master list of employees is stored in a different table to the master list of customers.įortunately, this requirement can be completed via the use of a dynamic SQL View.įirstly, create your record in App Designer as normal, setting the record type to ‘Dynamic View’. In this case, you would want a different prompt record depending on which radio button was selected. A single ‘ID’ field exists on the page, along with a radio button to specify ‘Employee’ or ‘Customer’.
For instance you may have a report run control page that works for both employees and customers. However, you may be faced with a requirement where the prompt record cannot be known in advance. In the above example, the prompt record has been defined as COUNTRY_TBL, an SQL Table. The prompt record is usually an SQL Table or SQL View. The prompt edit must be linked to a record, which does the job of filtering the data (if required). Such a field will appear on the page with a magnifying glass symbol on the right-hand side:īy clicking the symbol, users can select their desired value from a predefined list. If you’ve done a PeopleTools training course (or have equivalent experience), you will know that any field included on the page can be created with its own prompt table. PeopleTools | Setting up a field prompt based on SQL text created dynamically