As mentioned before, I've recently started working for a firm, creating applications in OpenEdge Progress-4GL.
One of the basic things we're doing here is putting a fill-in field on the screen, where we can fill in the value of an entry in a table.
Let's have a look at the following table, as an example:
employee_name employee_number
============= ===============
Dominique 001
Carl 002
Charlize 003
Freddy 004
My company's fill-in field handles the following features:
Enter the name of an employee ("Carl"), and the database jumps to the corresponding tuple in the database (002).
Press "Cursor-up" and the database jumps to the tuple just above (001).
Press "Cursor-down" and the database jumps to the tuple just underneath (003).
We are currently working with OpenEdge AppBuilder Release 11.6.
As far as general OpenEdge Progress software is concerned, we are working with OpenEdge Release 11.6 as of Fri Oct 16 19:01:51 EDT 2015.
I've just found out that we are simulating simple tab pages with checkboxes and visibility properties of basic components, which is extremely outdated, I'm looking to update this way of working, and I also wonder if there are newer ways to browse in a database, instead of working with the mentioned fill-in fields.
Does anybody have an idea if there are more recent controls I can use for this purpose?
The browse widget (static or dynamic), which can be associated with a query (that uses temp-tables or database tables) is the normal widget for showing data.
You can also use a .Net grid control with databinding.
Related
I’ve created an add-in that consist of a ribbon and three tabs.
Background to build:
The ribbon is built using designer and not xml. The primary use of these is to allow quick opening of various email templates.
Tab0 adds a couple buttons to the built in TabMail
Tab1 is a new custom tab with various buttons that do various things.
Tab2 is a reduced version of Tab1 for use by users of our subsidiary company but pointing to alternatively branded templates.
In the coding, Tab1 and Tab2’s visibility is set based on user AD group membership on ribbon load event. This has been tested and works.
Tab0 always is merged with the built in Home tab shows as expected.
Developers and template admins like me should see all tabs. This also works using same methods.
Current issue:
Recently and I think after a certain office 365 update (but not 100% which), Tab1 no longer shows for anyone that should see it on load. However the tab has loaded somewhere. The reason I know this is because to fix this bug all I have to do is minimise the ribbon the re-maximise. Both additional tabs are instantly visible.
Please note, I do not have to disable and the re-enable the actual add-in.
I can also confirm that the Ribbon Type is set correctly (Microsoft.Outlook.Explorer) so please, no reply along those lines either.
I have trawled the web and cannot seem to find an explanation or fix for this behaviour. I'm hoping someone has seen this before and might point me in the right direction.
To replicate, I've seen it happen by just creating a new simple ribbon project and creating a new custom tab. Then create a second tab by copying the first, giving it a diff ID.
e.g.
Ribbon on App Launch/Load - Tab01 Missing
Ribbon on minimise - Tab01 Appears
Ribbon on maximised- Tab01 still visible
Still have no idea why this happens but i have found a work around for those that have experiences the same issue.
The issue seems to affect the first custom tab only. So if you add a new blank custom tab and set its visibility to false, this inherits this bug allowing the other to function properly.
Its a bit of a dirty fix but work well.
Would still be interested in an actual fix if anyone knows one though.
This happens because you had added control to your ribbon perhaps a property to the Control which you should not.
An example is when you add a Ribbon Gallery control to your Ribbon and change its "PositionType" property from Default to another value.
This results in the Ribbon not showing.
Or perhaps you should check the last code you added to your project
Is there a way to present each detail row (at Master-Detail page) as separate tab or carousel slide? APEX 5.0
I've searched, read and tried for a whole evening, but nothing was found. Tradinional way is present region, not row as tab/carosel slide.
Apex 5.0 doesn't offer such a functionality. There might be some plug-in (search for it, if you want) but that's kind of a questionable solution because plug-in doesn't have to work in new Apex releases unless its designer upgrades it as well (or, alternatively, if you are capable of doing that).
If possible, upgrade to the most recent Apex version (currently, it is 19.x). There are numerous fancy stuff it offers, one of them being the Carousel Region. See how it looks like on the Universal Theme (Carousel Region) page. Or, create your own workspace on apex.oracle.com to see how it works.
In CRM Online 2015 Update 1 instances I experience charts on forms not showing the correct data until they are manually refreshed.
Charts in general show all data from the underlying view when the form is loaded. Only after manually refreshing a certain chart does it show "Only Related Records".
As an example, I have added a chart to the Account entity as seen below. Both the chart and the shown subgrid are using the same view. Even though there is only 1 related record the chart shows all data from "My Open Opportunities" after form load:
After refreshing the chart by clicking the small recycle-icon the correct data related to the current record (in this case 1) is shown:
I have tested this in 3 different CRM Online 2015 Update 1 instances which all exhibit the same behavior. Additionally, this is seen for both system and custom entities.
A similar chart setup in CRM Online 2015 without Update 1 works as expected.
I've got the same problem.
Microsoft has changed how they load forms. For now, you can switch back to the old way by going to Settings -> Administration -> System Settings -> General tab, and selecting Yes for “Use legacy form rendering”
This is only a temporary measure as that option is likely to be removed, but maybe Microsoft will support charts in forms or whatever the issue is by then.
PS:
Drawback is that the new way of loading forms is much faster, so you'll lose som e time if you switch back.
I Haven't tested this yet, but maybe you could add some javascript on the onLoad event to automatically select the view, like your users have to do now manually:
Xrm.Page.getControl(subgridname).getViewSelector().setCurrentView(viewname);
but this isn't pretty either
This issue is supposed to be fixed in Service Update 1 for Microsoft Dynamics CRM Online 7.1.1. From the changelog: "Charts within a subgrid are displaying all records when they should actually display only related records.".
The expected release date is around the middle of December.
I have Lightswitch 2013 and need to have nested autocomplete boxes. All the examples on the Internet are for older versions of Lightswitch and there are just a few differences in their examples from my version. Example: When adding Data Item for Local Property, Type "someTable" (Entity) doesn't come up as a choice. Also, if I click on one of my tables, then when I drag this Local Property to the screen is doesn't create an autocomplete box. Seems simple, but frustrating when I've tried many different ways. Please provide specific example using Lightswitch 2013. Thanks in advance. Steve
The steps are:
(1) Create a table called Customers(Id, Name) and a table called Orders(Id, CustomerId, Description) Create a foreign key relationship between Customers.Id and Orders.CustomerId.
(2) Update your LightSwitch 2013 Data Source
(3) Create an Add/Edit screen using the Orders table.
(4) By Default, all the fields (Id, Customer, Description) should be included. The Customer field should default to 'Details Picker' (The Choices will be 'Auto' and will lookup Customers in the Customers table)
Note: The Details Picker will AutoComplete after you type a minimum of three characters.
Thanks for the answer. I figured it out myself. I played around with displaying fields on my screens to see what was actually happening until I finally found out that I can add a specific data binding? to my properties and didn't have to use the drop down choices. I've got it working now.
This seems like a basic requirement for using Lightswitch. I wish someone would be able to post a detailed step by step solution to properly using nested autocomplete boxes. I'm not sure I would remember how to do nexted autocomplete boxes if I had to do this again in a year.
When an expert, like a Beth Massi, provides a detailed example for a specific version of Visual Studio or Lightswitch, it would be nice if that expert, or his/her replacement, would provide a new detailed example whenever Visual Studio or Lightswitch has a new version. Thanks for all the help I have received by searching the Internet.
We've just set up Dynamics CRM 2013. We're using the Outlook 2010 plug-in. A new entity has been created called "Projects," in which the users give the project a name (which is fairly long: Typically something like "2014 Project Name Client Name") and we assign activities and track emails to that project. The problem is that the project name in the blue bar doesn't truncate; instead it spills over the drop-down arrow (which lets you see related activities, contacts, etc) and is un-clickable. Logging in through the web interface, it truncates properly. Is there a way we can force it to truncate after a certain amount of letters, or use the ProjectID field for that label instead of the name? I'm fairly new to Dynamics so a simple solution would be much, much preferred.
A screenshot with an arrow pointing to the over-running field:
We had the same problem when using IE8. In IE9, the long name is truncated properly so the related button/link/whatever it is works as expected. MS unlikely to fix this issue in IE8 just fyi. If it's a custom entity, the primary key field will be the name and that field is used in the UI when it wants to show a record. So you have two options. Change the browser version or only use short names.