Perfrom action based on user input without custom dialog in filemaker - concurrency

I am developing a database solution in Filemaker Pro 16. I have a "customers" and "projects" table.
What I want to achieve is the following:
User clicks on a button
New window appears in which the user selects a customer from a drop down list
New project will be created
New window appears in which the user can enter the project information.
How can I do this. One can think, of course of an additional table in which temporary values are stored. In that case, I can store my customer selection in this table. However, what about concurrency. What if two people are going to add a project at the same time? In that case you would need a temporary values table for each user.
The most straightforward solution would be to directly store the selected customer in a variable. However, I don't think you can do that.
PS: I don't want to use a Custom Dialog. In that case, I think, you cannot add a drop down list.
Hope someone can help!

Use a Popover button for your customer selection.
Place your Drop Down list in the Popover panel, and store the Customer ID in a global field (they are local for each user).
Perform your script and navigate to your project layout upon selection, for instance using an OnObjectModify Script Trigger.

Related

How to launch customized form from code in Epicor ERP 10?

I’m working on customization where I prepared customized Customer form and Case Entry form.
In the Case Entry I have button that should launch customized Customer form.
Is it any other way to do it than adding new menu item for customized Customer?
Assuming I have understood your question correctly, a very similar question was asked on EpiUsers: https://www.epiusers.help/t/launch-customized-form-code/62207/5
Here's a snippet from the post. The link gives a lot more info with screenshots:
You can always create a New Menu ID under Processes section of the tree in Menu Maintenance, so it won’t show up on Menu selection, but then you can call it via code.
Is there a way to call it without adding it, I am sure one could debug what Epicor calls when you enter Customization Mode and select a layer. I believe its possible, I just haven’t taken the time to debug it, because I always use the Menu Maintenance instead, because layer names change and relying on a special layer name is more fragile than adding a Menu Item under Processes section in Menu Maintenance – Plus then you can re-purpose the same Menu ID everywhere easily, without hardcoding layer names.
This way, you can keep the standard Customer form in place on the menu, but use the button to launch the customization. Hope this helps!

Can I dynamically disable a drilldown in Siebel 7.8?

I have a list applet with a drilldown in one of the columns, and I want to enable or disable it based on another field's value. Something like a dynamic drilldown, but instead of choosing a different view, I want to disable the navigation for some of the records.
Can this be done in Siebel 7.8?
Ideally without server scripting... and definitely without ugly browser scripting hacks, please.
I have tried creating a dynamic drilldown, but it doesn't work because I have to specify a target view in my parent default drilldown. If I use an inactive view for that, then the whole dynamic drilldown is ignored and Siebel simply uses the one with the next sequence number.
I can think of a couple of ways to implement it, but both are far from ideal:
Writing some server script to detect the drilldown event before it happens, and abort it if needed with a RaiseErrorText message. It should be doable... but I'd rather disable the drilldown than throw an ugly error to my users.
Placing the drilldown in a calculated field, and make it have no text when there should be no navigation. If there is no text, there is nothing the users can click to drilldown, right? But I would have to add a new column just for the drilldown, which would be confusing for the users.
If you don't want any scripting. There are 2 ways.
First way is using toggle applet.
1.Main Applet will have the drill down down object. And Toggle applet will not have the drill down objects.
2.Create a field in the BC to use it in the Toggle Applet condition .Toggle Applet will be displayed when the drilldown is not required.
Second way you can achieve it is through visibility Type attribute in the drilldown object as well as visibility Applet Type attribue at the view level.

How can you edit Sitecore desktop shortcuts?

Anyone know how to edit the name of the Sitecore desktop shortcuts? I'm using the Advanced System Reporter module, and creating a desktop shortcut from there, but now I can't change the name of the item.
I know that you can right click on the Sitecore desktop shortcut and choose properties so change the information of the link....but how can I change the name of the shortcut?
The properties have a field 'Name', that even when I change it, the shortcut doesn't change (even after a desktop refresh).
I tried changing the 'Link' field on the properties as well, but then the link disappeared.
Do these exist in the core database somewhere? Can I get back the one that I just lost (by changing the Link field)?
Through further research, I found that for normal links, the name can be edited by right clicking the link, selecting 'Properties' and changing the 'Name' field.
Unfortunately, Links generated through the Advanced System Reporter don't update on the desktop when this Name property is changed.
It seems that the links for these desktop shortcuts are a combination of items in the core database and values in the User profile in the aspnet_profile DB table (also in core, but only viewable through SQL).
This value is stored in the PropertyValueBinary field, which, as the name suggests, is all in binary, and can't (or shouldn't) be edited.
One way around this is to:-
Create the desktop link, which will be called something by default (i.e 'SalesReport').
Open up the core database in Sitecore, and navigate to /sitecore/content/Applications/Advanced System Reporter/Links. Then find the folder for your username.
Find the item that was created for the link (in this case it'll be 'SalesReport'), and change the value of the field 'Display name' to whatever you want the link called (i.e 'Sales Report for May'.
Note: You may want to change the name of the item as well, so that it won't get lost in other desktop links created in the future and will be easier to find later. In this case you will need to:-
Go back to the desktop, right click the shortcut and choose Properties.
Manually change the end of the 'Link' field to the name you want to call the item (i.e change it from 'SalesReport' to 'Sales Report for May'.)
When you click OK, the shortcut will disappear. This is expected.
Open up the core database in Sitecore again, and find the item you're changing. (i.e /sitecore/content/Applications/Advanced System Reporter/Links/SalesReport
Change the name to exactly what you changed it to in step 2.
The link will reappear on the desktop, it'll have the correct name, and will be easy to locate in the Sitecore DB in the future.

Avoid report to allow modifications of records in Filemaker Pro 11

I'm building a database that needs to display tables as lists and allow the user to export such lists as Excel spreadsheets.
Creating the reports, showing them as lists and providing the button for exporting as Excel was not a problem, however I noticed that when I show those lists the user can still edit them, hence add/deleting records and modify the content of existing records.
I'd like to find a way to avoid such modifications when visualizing the list, in such a way to be sure the user does not accidentally change data.
Any idea as to how to do this? I'm using Filemaker pro 11
Thanks in advance.
There are a couple of different ways that might be appropriate, depending on your needs:
In layout mode, click on the field, go to the Data tab of the Inspector, and turn off field entry in 'Browse' mode. (You also have the option to turn off field entry in 'Find' mode. And you can select multiple fields at once to make the selection for all of them.) This is appropriate if your users can regularly enter data into these fields but you don't want them to enter data for this particular layout.
In Manage Database, under the field options, turn on Prohibit modification of value during data entry in the Auto-Enter tab. This is appropriate if you will only be changing the value of a field during an import or with a script.
In Manage Security, create a new Privilege Set that is View-Only for that table (or for those fields). This is appropriate when some users should be able to modify the data and other users should not be able to modify the data.
There are other methods, as well, but those are the three most common for limiting user access to data.

Add Activities to Activity Dropdown in Task Work Item

Is there a way to modify the values that are currently in the Activity dropdown for a Task work item? Here's the current list:
Deployment
Design
Development
Documentation
Testing
Requirements
Sure, you have to edit the Process Template or the Work Item type of the existing Team Project you want to change.
This article gives you information about how to edit a Process Template.
If you want to edit the Work Item of an existing team project is almost the same process, only the start is different as you have to select this command:
Once your Task Work Item Type is selected, double-click on the Activity field in the Fields tab.
Then in the windows that opens, go to the "Rules" tab and double-clik on the "SUGGESTEDVALUE" line.
Then change the lines you want.
Finally save the Work Item type, if you're from the process template then follow the procedure told in the article, if you're from the Work Item in an existing Team Project, you just have to save for the change to be effective.
BUT, beware (for the existing Team Project case) that if some Work Items already exist in your Team Project that use a value you removed, these ones will generate an error the next time you'll edit them. You'll have to change the value of the Activity field to an existing one if you want the Work Item to be save-able.