Is it possible to add custom fields useable for all projects, but have the values linked with the project, so that when creating issues the dropdown list shows only the values which have been used for that project, like the target version which is linked with a project?
This feature is not yet implemented in Redmine.
My solution will be to prefix the branch name with a short code for the project and that way the field can be used for all projects, eg PROJABBREVIATION_branchA. Hopefully the prefixes won't be too awkward.
Related
I am trying to change the server for several dozen reports, all developed by different people, that use a mix of:
Shared Datasources (have a query for this)
Custom Data Sources in RDLs (not perfect but I have a PowerShell script that will download all reports, then I can them search them with Notepad++)
Custom Data Sources that are overridden on the SSRS Server.
Does anybody have a way to find the details of the Custom Data Sources? Shared is easy. I need to get the details of the CUSTOM. Tried going through the data sources table but it's not standard varbinary.
And hey, bonus fake internet points if you have a way to update the custom DS as well; I already have code to change the shared ones.
Good Morning,
as from the title, i'd like to create a proprietary database to be integrate in a Typo3 website.
I'd like to receive some advise on which is the best solution:
- is it possible to create tables directly from Typo3?
- is it better creating a database, for example with MySQL and then integrate
it?
In the second case, how coud that be done?
are there other options?
I hope this is not an already answered topic, in case, please send me to it ( i could not find so much information.
Thanks in advance.
If I understand your question correctly, you want to add a custom Extension to TYPO3, containing custom tables. From a content side, this is perceived as a "database", right?
TYPO3 has a framework for that called Extbase. You can "kickstart" a TYPO3 extension with the "Extension Builder" https://typo3.org/extensions/repository/view/extension_builder by entering the "Model" (the data structure) via GUI and then you get all tables etc. automatically set up.
After that (aside from general TYPO3 knowledge), there is some coding involved. In theory, it's possible to make a "round trip" back to the extension builder from the code, but I've never done that.
You need to know / learn the specificities of extbase / php, which is is based on some "convention over configuration" rules and has some additional tweaks to plain PHP (functional comments). Here's a great resource: http://www.extbase-book.org/.
With that, you have great flexibility and powerful tooling to build almost anything inside TYPO3.
From a TYPO3 view it is best if you are able to hold your data in the TYPO3 database. You need to create an extension to handle your data. In TYPO3 an extension can define it's own tables and with updates of the extension updates in the datastructure are handled automatically.
Since version 8 there is a new layer (doctrine) and so it is possible to define further databases for individual tables. With some restrictions you are able to even use different database (-systems) for different tables.
Anyway you could program your own database interface to get and store your data independent from any TYPO3 restrictions, but then you need to handle everything on your own.
Using the TYPO3 core API will help you in multiple ways to handle your data without programming everything anew.
Especially if you use extbase (and the EXT:extensionbuilder) you will get a complete BE data handling, FE-Plugins with Fluid templates to present your data, even data management from the FE could be generated for you just by defining the datastructure. Of course versioning, workspace and timed visibility support are also available if you use TYPO3 structures which includes some (mostly invisible) fields aside from uid, hidden, deleted.
I am using a software powered by SugarCRM. The reports I show are not very good so I decided to user Pentaho BI Suite. I already made all the business analitycs stuff (cubes, reports, saiku report, etc..), but I am having an issue, in SugarCRM database, the label's values of some dropdownlist (for example), are not storaged. Instead they are written in a .JS file y the sugar directory called sp_ve.js like this :
SUGAR.language.SetLanguage('app_string',[JSON OBJECT WITH THE LABELS VALUES]) ;
SUGAR.language.SetLanguage('app_list_strings',[JSON OBJECT WITH LABEL VALUES]);
Now, is there any way to insert those objects into tables, so I can use it in my OLAP solution in pentaho?, HOW? . If yes, how can I make this process work automatically, every time my users add new labels.
First of all, all the dropdowns, text labels, etc. actually stored in <lang_key>.lang.php files under <sugar_root>/include/language/ and <sugar_root>/custom/include/language/ directories. And only then those labels become accessible with JavaScript used in SugarCRM UI. See this page for more information.
For similar situation of preparing SugarCRM database for analyzing with Tableau Desktop Professional I decided to use the following approach.
At the beginning all the dictionaries/mappings needed in files mentioned above were extracted into separate CSV files. You can do it with text editor of your choice using find/replace. Then those CSV files were imported into SugarCRM database as new tables - one table for each list. After that I used database view to join "data" table with "label map" table and used that view as a source for my analytical needs. Yes, it's not so elegant and dynamic solution. Moreover it needs a little hand work. But it solves the issue.
In Access 2007 I create a lot of custom groups to organise the large number of queries and tables in a single database. There are lots of individual sub queries that link up to larger queries. In development, I find it necessary to frequently rename some of the queries permanently after they have been added to a custom group.
But Access only renames the shortcut that is in the group and not the actual object. This causes broken references. So I now have to remove an object from the group, rename it, then add back to the group. This adds further problems if you have lots of queries and tables.
Is there any way to configure Access to rename the actual object and not just the shortcut from within a custom group?
Thanks
You cannot do this in Access 2007 version, at least.
Yes, it is possible.
Delete the shortcut, so the object is located in the unassigned objects group. In there, rename the object. Then drag the object back in the customized group.
This is possible to do without deleting anything. Here's how:
Switch the view type in the navigation panel to the type of object you're working with (queries or tables)
find the actual table and rename it (everything you see here will be actual objects and not shortcuts)
switch the view type back to Custom
This will change the name of the table while keeping the name of the shortcut in tact. I tested this in Access 2013, and the old shortcut will now point to the new table name.
Unfortunately, you cannot do this in Access. That's the idea of shortcuts. Actually, it is the same as in Windows (you can rename the shortcut but the object itself stays intact).
The short answer to your question - NO
First a bit about the environment:
We use a program called Clearview to manage service relationships with our customers, including call center and field service work. In order to better support clients and our field technicians we also developed a web site to provide access to the service records in Clearview and reporting. Over time our need to customize the behavior and add new features led to more and more things being tied to this website and it's database.
At this point we're dealing with things like a Company being defined partly in the Clearview database and partly in the website database. For good measure we're also starting to tie the scripting for our phone system into the same website, which will require talking to the phone system's own database as well.
All of this is set up and working... BUT we don't have a good data layer to work with it all. We moved to Linq to SQL and now have two DBMLs that we can use, along with some custom classes I wrote before I'd ever heard of Linq, along with some of the old style ADO datasets. So yeah, basically things are a mess.
What I want is a data layer that provides a single front end for our applications, and on the back end manages everything into the correct database.
I had heard something about Entity Framework allowing classes to be built from multiple sources, but it turns out there can only be one database. So the question is, how could I proceed with this?
I'm currently thinking of getting the Linq To SQL classes all set for each database, then manually writing Linq compatible front ends that tie those together. Seems like a lot of work, and given Linq's limitations (such as not being able to refresh) I'm not sure it's a good idea.
Could I do something with Entity Framework that would turn out better? Should I look into another tool? Am I crazy?
The Entity Framework does give a certain measure of database independence, insofar as you can build an entity model from one database, and then connect it to a different database by using a different entity connect string. However, as you say, it's still just one database, and, moreover, it's limited to databases which support the Entity Framework. Many do, but not all of them. You could use multiple entity models within a single application in order to combine multiple databases using the Entity Framework. There is some information on this on the ADO.NET team blog. However, the Entity Framework support for doing this is, at best, in an early stage.
My approach to this problem is to abstract my use of the Entity Framework behind the Repository pattern. The most immediate benefit of this, for me, is to make unit testing very simple; instead of trying to mock my Entity model, I simply substitute a mock repository which returns IQueryables. But the same pattern is also really good for combining multiple data sources, or data sources for which there is no Entity Framework provider, such as a non-data-services-aware Web service.
So I'm not going to say, "Don't use the Entity Framework." I like it, and use it, myself. In view of recent news from Microsoft, I believe it is a better choice than LINQ to SQL. But it will not, by itself, solve the problem you describe. Use the Repository pattern.
if you want to use tools like Linq2SQl or EF and don't want to have to manage multiple DBMLS (or whaetever its called in EF or other tools), you could create views in your website database, that reference back to the ClearView or Phone system's DB.
This allows you to decouple your web site from their database structure. I believe Linq2Sql and EF can use a view as the source for an Entity. If they can't look at nHibernate.
This will also let you have composite entities that are pulled from the various data sources. There are some limitations updating views in SQL Server; however, you can define your own Instead of trigger(s) on the view which can then do the actual insert update delete statements.
L2S works with views, perfectly, in my project. You only need to make a small trick:
1. Add a secondary DB table to the current DB as a view.
2. In Designer, add a primary key attribute to a id field on the view.
3. Only now, add an association to whatever other table you want in the original DB.
Now, you might see the view available for the navigation.